postgresql-interfaces/psqlodbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: abhi-555 (@abhi-555) <[email protected]>
To: postgresql-interfaces/psqlodbc <[email protected]>
Subject: Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
Date: Tue, 20 May 2025 04:37:29 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[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);

view thread (11+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://postgresql-interfaces/psqlodbc
  Cc: [email protected], [email protected]
  Subject: Re: [postgresql-interfaces/psqlodbc] issue #92: SQLSpecialColumns not working as expected in the shared standalone
  In-Reply-To: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox