Re: Can't run CREATE PROCEDURE with new Postgres' 14 new SQL-standard body - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Can't run CREATE PROCEDURE with new Postgres' 14 new SQL-standard body
Date
Msg-id CADK3HHJQKArsRJbRWybewLOcw6pWHFecSzFJD2RrP+TEDOFRSw@mail.gmail.com
Whole thread Raw
In response to Re: Can't run CREATE PROCEDURE with new Postgres' 14 new SQL-standard body  (Thomas Kellerer <shammat@gmx.net>)
List pgsql-jdbc


On Mon, 4 Oct 2021 at 11:27, Thomas Kellerer <shammat@gmx.net> wrote:
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

Serhope,

We should probably document this..

Dave Cramer
www.postgres.rocks
 

pgsql-jdbc by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: Can't run CREATE PROCEDURE with new Postgres' 14 new SQL-standard body
Next
From: Dave Cramer
Date:
Subject: [pgjdbc/pgjdbc] daeea3: fix spacing on GSS_ENC_MODE (#2280)