Re: Prepared Statements - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: Prepared Statements
Date
Msg-id 3944.1058853363@sss.pgh.pa.us
Whole thread Raw
In response to Re: Prepared Statements  (Peter Kovacs <peter.kovacs@siemens.com>)
Responses Re: Prepared Statements  (Peter Kovacs <peter.kovacs@siemens.com>)
List pgsql-jdbc
Peter Kovacs <peter.kovacs@siemens.com> writes:
> I think that the simplest thing would be to have an option in the
> backend to disable processing of multiple statements in one query --
> i.e. disallow the use of ';' as a separator of statements.

FWIW, the new "extended query" protocol has exactly such a restriction.
However that hardly excuses any sloppiness in allowing
non-syntax-checked parameter values through.  Consider changing
"WHERE x < ?" to
"WHERE x < 42 AND my_function_with_interesting_side_effects()"

No semicolons in sight, but I can still clean out your bank balance ;-)

            regards, tom lane

pgsql-jdbc by date:

Previous
From: "David Wall"
Date:
Subject: Detecting 'socket errors' - SQLSTATE patch
Next
From: peter royal
Date:
Subject: Re: the IN clause saga