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

Поиск
Список
Период
Сортировка
От Kris Jurka
Тема Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)
Дата
Msg-id Pine.BSO.4.64.0904210324180.1019@leary.csoft.net
обсуждение исходный текст
Ответ на Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)  ("j.random.programmer" <javadesigner@yahoo.com>)
Список 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 по дате отправления:

Предыдущее
От: "j.random.programmer"
Дата:
Сообщение: Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)
Следующее
От: "j.random.programmer"
Дата:
Сообщение: Re: Bug with duplicate column names via JDBC MetaData (ORDINAL_POSITION)