SQLSpecialColumns not working as expected in the shared standalone

[abhi-555]

After using the fix provided in #79

I am still receiving zero rows upon running SQLSpecialColumns in the given test case in the shared standalone.

Can you please run the test case in the standalone SQLSpecialColumns.zip and confirm if this is working for you?

Test case
CREATE TABLE test_special( id integer, ival integer);
CREATE UNIQUE index test_special_id on public.test_special(id);
CREATE UNIQUE index test_special_ui on public.test_special(ival);

[davecramer]

Yes, can confirm that it does not work. I'm at odds as the test case does work. Looking into it.
Dave

[abhi-555]

Can you please provide any updates on this?

[davecramer]

Hi,

I'm stuck trying to debug this. It works fine in the test cases for ODBC, however in a standalone program it doesn't.

I'm still working on it.

[davecramer]

@abhi-555 I just merged a PR that should fix this. Please let me know

[abhi-555]

I have tested this. I am not getting the column name but the schema name in the result set. We are binding the result set to the second column in the query. Isn't that supposed to be column name according to the ODBC standard?

[davecramer]

you are correct, sorry about that. I'll try to get something out in the next few days

[davecramer]

OK just merged in #109 which should fix this.