Re: SET prepared statement - Mailing list pgsql-general

From David G. Johnston
Subject Re: SET prepared statement
Date
Msg-id CAKFQuwbMaoO9=VUY1K0Nz5YBDyE6YQ9A_A6ncCxD+t0yK1AxJg@mail.gmail.com
Whole thread Raw
In response to SET prepared statement  (Oliver Kohll <oliver@agilechilli.com>)
Responses Re: SET prepared statement
List pgsql-general
On Wed, Apr 13, 2016 at 8:38 AM, Oliver Kohll <oliver@agilechilli.com> wrote:
Hello,

We currently use prepared statements for most of the work an app does, as an SQL injection protection and for other reasons.

There's one statement which can't be prepared:

SET LOCAL myprefix.mysetting = 'my setting value';

Ideally, I'd like to be able to do

PREPARE test(text) as SET LOCAL myprefix.mysetting = $1;

but this isn't supported (currently on PG 9.3)

I suspect the answer is 'no' but no harm in asking if it's likely to be considered in future. I can't see it here: https://wiki.postgresql.org/wiki/Todo


​Given that you can simply use the "set_config(...)" function I'd say that this command will have not particular in the decision work on improving this limitation in the system.


​David J.​

pgsql-general by date:

Previous
From: Alex Ignatov
Date:
Subject: Re: Freezing localtimestamp and other time function on some value
Next
From: Alex Ignatov
Date:
Subject: Re: Freezing localtimestamp and other time function on some value