Re: jdbc driver return wrong medata values

From: Kris Jurka <books(at)ejurka(dot)com>
To: Xavier Maysonnave <xavier(at)omondo(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: jdbc driver return wrong medata values
Date: 2005-04-15 19:14:56
Message-ID: Pine.BSO.4.56.0504151413490.10068@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 14 Apr 2005, Xavier Maysonnave wrote:

> postgresql-8.0-311.jdbc3.jar
>
> While analysing the index structures of a metadata table with the
> following statement :
>
> ResultSet parts = dbMeta.getIndexInfo("aCatalog", "aMetaSchema",
> "aTable", false, false);
> ...
> if (parts != null) {
> try {
> while (parts.next()) {
> String indexName = parts.getString(6);
> String columnName = parts.getString(9);
> short position= parts.getShort(8);
> String direction = parts.getString(10);
> boolean unique = parts.getBoolean(4);
> }
> } finally {
> parts.close();
> }
> }
>
> While controling the result with pgadmin III it appears that :
>
> - Unique Index have a returned boolean unique set to false :
> - this value should apply to Non Unique Index
> - Non Unique Index have a returned boolean unique set to true :
> - this value should apply to Unique Index
>

If you check the javadoc for getIndexInfo you will see column four is
actually "NON_UNIQUE" not unique.

Kris Jurka

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dirar Abu Kteish 2005-04-16 12:49:01 BUG #1601: removing columns
Previous Message David McClellan and Alun Prytherch 2005-04-15 19:06:35 BUG #1600: Interrupt routine causes libPQ call to fail w/o error