Unexpected Statement Caching with CURRENT_TIMESTAMP

Поиск
Список
Период
Сортировка
От Nicholas E. Wakefield
Тема Unexpected Statement Caching with CURRENT_TIMESTAMP
Дата
Msg-id 2F2A7EB72EBAF24582513E72ACCBCAAE17D8C9@kniexch01.KineticNetworks.com
обсуждение исходный текст
Ответ на Re: SQL query never ends  (Mark Lewis <mark.lewis@mir3.com>)
Ответы Re: Unexpected Statement Caching with CURRENT_TIMESTAMP
Re: Unexpected Statement Caching with CURRENT_TIMESTAMP
Список pgsql-jdbc
I'm executing 'SELECT CURRENT_TIMESTAMP' from a statement object with
auto commit off and prepare threshold set to 1. I'm finding that the
result comes back the same for after multiple calls and instantiations
of the statement object(The same happens for a prepared statement).
However this does not occur when I perform a commit before or after
every call.

Is this expected behaviour?

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

Предыдущее
От: Mark Lewis
Дата:
Сообщение: Re: SQL query never ends
Следующее
От: Dave Cramer
Дата:
Сообщение: Re: Unexpected Statement Caching with CURRENT_TIMESTAMP