From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
---|---|
To: | Thomas Kellerer <shammat(at)gmx(dot)net> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org>, Sehrope Sarkuni <sehrope(at)jackdb(dot)com> |
Subject: | Re: Can't run CREATE PROCEDURE with new Postgres' 14 new SQL-standard body |
Date: | 2021-10-05 13:03:33 |
Message-ID: | CADK3HHJQKArsRJbRWybewLOcw6pWHFecSzFJD2RrP+TEDOFRSw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Mon, 4 Oct 2021 at 11:27, Thomas Kellerer <shammat(at)gmx(dot)net> wrote:
> Sehrope Sarkuni schrieb am 04.10.2021 um 14:49:
> > On Sun, Oct 3, 2021 at 8:08 AM Thomas Kellerer <shammat(at)gmx(dot)net <mailto:
> shammat(at)gmx(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2021-10-05 14:57:24 | [pgjdbc/pgjdbc] daeea3: fix spacing on GSS_ENC_MODE (#2280) |
Previous Message | Thomas Kellerer | 2021-10-04 15:27:32 | Re: Can't run CREATE PROCEDURE with new Postgres' 14 new SQL-standard body |