Re: Can't run CREATE PROCEDURE with new Postgres' 14 new SQL-standard body
От | Thomas Kellerer |
---|---|
Тема | Re: Can't run CREATE PROCEDURE with new Postgres' 14 new SQL-standard body |
Дата | |
Msg-id | 12605f56-a371-04cd-1b65-ea2eb12ad835@gmx.net обсуждение исходный текст |
Ответ на | Re: Can't run CREATE PROCEDURE with new Postgres' 14 new SQL-standard body (Sehrope Sarkuni <sehrope@jackdb.com>) |
Ответы |
Re: Can't run CREATE PROCEDURE with new Postgres' 14 new SQL-standard body
|
Список | pgsql-jdbc |
Sehrope Sarkuni schrieb am 04.10.2021 um 14:49: > On Sun, Oct 3, 2021 at 8:08 AM Thomas Kellerer <shammat@gmx.net <mailto:shammat@gmx.net>> wrote: > > Postgres 14 supports SQL standard conforming bodies for functions and procedures > which are no longer string constants, e.g. > > create or replace procedure do_stuff() > language sql > begin atomic > select 1; > select 2; > end > > However, it seems that the JDBC driver will parse the string and split it into > multiple statements based on the semicolons thus making it an invalid create procedure > statement. > > > If you set the connection property "preferQueryMode" to "simple" or > "extendedForPrepared", then the driver will not attempt to split the > statement into multiple commands. Thanks, that works fine. Changing the connection URL is a good enough solution for me. Thomas
В списке pgsql-jdbc по дате отправления: