Message-ID: <gh-postgresql-interfaces-psqlodbc-92-c2892913852@github.com>
From: "abhi-555 (@abhi-555)" <noreply+abhi-555@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Tue, 20 May 2025 04:37:29 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-92@github.com>
References: <gh-postgresql-interfaces-psqlodbc-92@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: abhi-555
X-GitHub-Comment-Id: 2892913852
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 92
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/issues/92#issuecomment-2892913852
Content-Type: text/plain; charset=utf-8

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);