postgresql-interfaces/psqlodbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feed[postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
11+ messages / 2 participants
[nested] [flat]
* [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-02-18 10:55 "abhi-555 (@abhi-555)" <[email protected]>
0 siblings, 0 replies; 11+ messages in thread
From: abhi-555 (@abhi-555) @ 2025-02-18 10:55 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
After using the fix provided in https://github.com/postgresql-interfaces/psqlodbc/issues/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](https://github.com/user-attachments/files/17919927/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);
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-02-21 14:10 ` "davecramer (@davecramer)" <[email protected]>
9 siblings, 0 replies; 11+ messages in thread
From: davecramer (@davecramer) @ 2025-02-21 14:10 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
Yes, can confirm that it does not work. I'm at odds as the test case does work. Looking into it.
Dave
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-03-11 05:20 ` "abhi-555 (@abhi-555)" <[email protected]>
9 siblings, 0 replies; 11+ messages in thread
From: abhi-555 (@abhi-555) @ 2025-03-11 05:20 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
Can you please provide any updates on this?
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-03-11 13:25 ` "davecramer (@davecramer)" <[email protected]>
9 siblings, 0 replies; 11+ messages in thread
From: davecramer (@davecramer) @ 2025-03-11 13:25 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
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.
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-03-12 14:38 ` "davecramer (@davecramer)" <[email protected]>
9 siblings, 0 replies; 11+ messages in thread
From: davecramer (@davecramer) @ 2025-03-12 14:38 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
@abhi-555 I just merged a PR that should fix this. Please let me know
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-04-14 05:23 ` "abhi-555 (@abhi-555)" <[email protected]>
9 siblings, 0 replies; 11+ messages in thread
From: abhi-555 (@abhi-555) @ 2025-04-14 05:23 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
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?
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-04-15 18:45 ` "davecramer (@davecramer)" <[email protected]>
9 siblings, 0 replies; 11+ messages in thread
From: davecramer (@davecramer) @ 2025-04-15 18:45 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
you are correct, sorry about that. I'll try to get something out in the next few days
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-04-16 01:36 ` "davecramer (@davecramer)" <[email protected]>
9 siblings, 0 replies; 11+ messages in thread
From: davecramer (@davecramer) @ 2025-04-16 01:36 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
OK just merged in #109 which should fix this.
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-05-20 04:37 ` "abhi-555 (@abhi-555)" <[email protected]>
9 siblings, 0 replies; 11+ messages in thread
From: abhi-555 (@abhi-555) @ 2025-05-20 04:37 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
I tested the fix. It is working in cases when there is only one unique index on the table. However, if there are two(multiple) unique indexes on the table, we are getting columns from both the indexes in the result which is not the correct behaviour according to my understanding.
We should ideally only get columns from one index in the result. Can you please check this case? Below is the use case for reference
CREATE TABLE public.users (
id integer
username VARCHAR(40),
email VARCHAR(50),
);
CREATE UNIQUE INDEX idx_users1 ON public.users(username);
CREATE UNIQUE INDEX idx_users2 ON public.users(email);
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-05-20 11:45 ` "davecramer (@davecramer)" <[email protected]>
9 siblings, 0 replies; 11+ messages in thread
From: davecramer (@davecramer) @ 2025-05-20 11:45 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
Just read the docs, and you are correct. I will have a look shortly
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
@ 2025-06-12 09:55 ` "davecramer (@davecramer)" <[email protected]>
9 siblings, 0 replies; 11+ messages in thread
From: davecramer (@davecramer) @ 2025-06-12 09:55 UTC (permalink / raw)
To: postgresql-interfaces/psqlodbc <[email protected]>
I have committed code that should resolve this issue. Please let me know.
^ permalink raw reply [nested|flat] 11+ messages in thread
end of thread, other threads:[~2025-06-12 09:55 UTC | newest]
Thread overview: 11+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-02-18 10:55 [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone "abhi-555 (@abhi-555)" <[email protected]>
2025-02-21 14:10 ` "davecramer (@davecramer)" <[email protected]>
2025-03-11 05:20 ` "abhi-555 (@abhi-555)" <[email protected]>
2025-03-11 13:25 ` "davecramer (@davecramer)" <[email protected]>
2025-03-12 14:38 ` "davecramer (@davecramer)" <[email protected]>
2025-04-14 05:23 ` "abhi-555 (@abhi-555)" <[email protected]>
2025-04-15 18:45 ` "davecramer (@davecramer)" <[email protected]>
2025-04-16 01:36 ` "davecramer (@davecramer)" <[email protected]>
2025-05-20 04:37 ` "abhi-555 (@abhi-555)" <[email protected]>
2025-05-20 11:45 ` "davecramer (@davecramer)" <[email protected]>
2025-06-12 09:55 ` "davecramer (@davecramer)" <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox