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(at)commoninf(dot)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.
>
>
>