Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION) - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)
Date
Msg-id Pine.BSO.4.64.0904210324180.1019@leary.csoft.net
Whole thread Raw
In response to Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)  ("j.random.programmer" <javadesigner@yahoo.com>)
List pgsql-jdbc

On Tue, 21 Apr 2009, j.random.programmer wrote:

> Just to recap, this is on postgres 8.3.3 and JDBC3 8.3-604.
>
> null, pg_catalog, pg_ts_dict, dictname, 12, name, 2147483647, null, 0, 10, 0, null, null, null, null, 2147483647, 1,
NO,null, null, null, null 
> null, public, pg_ts_dict, dict_name, 12, text, 2147483647, null, 0, 10, 0, null, null, null, null, 2147483647, 1, NO,
null,null, null, null 

What you have is a pre-8.3 install that had the tsearch2 contrib module
installed that was upgraded to 8.3 with the core tsearch functionality.
If you look at the schemas in the above output or do \d *.pg_ts_dict you
will see two tables.

Kris Jurka

pgsql-jdbc by date:

Previous
From: "j.random.programmer"
Date:
Subject: Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)
Next
From: "j.random.programmer"
Date:
Subject: Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)