Re: Patch for Statement.getGeneratedKeys()

Поиск
Список
Период
Сортировка
От Ken Johanson
Тема Re: Patch for Statement.getGeneratedKeys()
Дата
Msg-id 478C4516.1000804@kensystem.com
обсуждение исходный текст
Ответ на Re: Patch for Statement.getGeneratedKeys()  (Kris Jurka <books@ejurka.com>)
Ответы Re: Patch for Statement.getGeneratedKeys()
Список pgsql-jdbc
>> is it is possible to determine the connection's db and schema
>> names to normalize those array elements (in the case where just the
>> [schema]tablename is provided). Is it possible without a round trip to
>> know what these should be?
>
> You can tell the connection's database via Connection.getCatalog, but
> there is no such thing as a connection's schema.  Each connection has a
> search_path that specifies the order it looks through schemas to find a
> table.  So you can't tell what schema a table is in without looking
> through the list.
>

That makes sense to me now, thanks. In any case do you agree that we
still need to parse the fully qualified table, in case of input like:

insert into postgres.public.test ...

I don think my earlier question about getting the current/default
catalog name is relevant since the query can specify other ones. True?



В списке pgsql-jdbc по дате отправления:

Предыдущее
От: Kris Jurka
Дата:
Сообщение: Re: setQueryTimeout
Следующее
От: Ken Johanson
Дата:
Сообщение: Re: Patch for Statement.getGeneratedKeys()