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

From j.random.programmer
Subject Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)
Date
Msg-id 687034.20430.qm@web31107.mail.mud.yahoo.com
Whole thread Raw
In response to Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)  ("j.random.programmer" <javadesigner@yahoo.com>)
List pgsql-jdbc
Hi:

> > 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.

Yes, that was the setup of my postgres...you diagnosed it *exactly*. Are you sure you are not a doctor in real life ?
:-)

Best regards,
--j




pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)
Next
From: "Peter"
Date:
Subject: JDBC problem with dates and ANYELEMENT type