Re: "Cached plan must not change result type" error whenswitching search_path via explicit execution of SET SEARCH_PATH = ...

Поиск
Список
Период
Сортировка
От Vladimir Sitnikov
Тема Re: "Cached plan must not change result type" error whenswitching search_path via explicit execution of SET SEARCH_PATH = ...
Дата
Msg-id CAB=Je-ESngGfwRVw-LN7-C27UjBv7tNSPM+3cTtgMVzOnCVARg@mail.gmail.com
обсуждение исходный текст
Ответ на [JDBC] "Cached plan must not change result type" error when switching search_path via explicit execution of SET SEARCH_PATH = ...  ("Al Presseller" <apresseller@commoninf.com>)
Ответы Re: "Cached plan must not change result type" error when switching search_path via explicit execution of SET SEARCH_PATH = ...  ("Al Presseller" <apresseller@commoninf.com>)
Список pgsql-jdbc
Дерево обсуждения
That's unfortunate.

Would you please report that ustream? (I mean to the postgresql developers)

The thing is it would be so much easier if pgjdbc would not have to parse SQL in order to identify if the statement was "set search_path".

In the mean time: is lowercase style fine for you?

Vladimir

ср, 25 янв. 2017 г. в 1:27, Al Presseller <apresseller@commoninf.com>:

The fix for issue #496 ("Cached plan must not change result type" when using PreparedStatement cache across schemas) doesn’t work when the default schema is being assigned via explicit execution of a SET statement that renders the search_path keyword in UPPER CASE.   

 

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

Предыдущее
От: "Al Presseller"
Дата:
Сообщение: [JDBC] "Cached plan must not change result type" error when switching search_path via explicit execution of SET SEARCH_PATH = ...
Следующее
От: "Al Presseller"
Дата:
Сообщение: Re: [JDBC] "Cached plan must not change result type" error when switching search_path via explicit execution of SET SEARCH_PATH = ...