| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | "j(dot)random(dot)programmer" <javadesigner(at)yahoo(dot)com> |
| Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION) |
| Date: | 2009-04-21 07:26:00 |
| Message-ID: | Pine.BSO.4.64.0904210324180.1019@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | j.random.programmer | 2009-04-23 04:10:54 | Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION) |
| Previous Message | j.random.programmer | 2009-04-21 07:19:23 | Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION) |