Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)

From: "j(dot)random(dot)programmer" <javadesigner(at)yahoo(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)
Date: 2009-04-23 04:10:54
Message-ID: 687034.20430.qm@web31107.mail.mud.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Browse pgsql-jdbc by date

  From Date Subject
Next Message Peter 2009-04-23 08:13:28 JDBC problem with dates and ANYELEMENT type
Previous Message Kris Jurka 2009-04-21 07:26:00 Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)