Re: SET prepared statement

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Oliver Kohll <oliver(at)agilechilli(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: SET prepared statement
Date: 2016-04-13 15:48:02
Message-ID: CAKFQuwbMaoO9=VUY1K0Nz5YBDyE6YQ9A_A6ncCxD+t0yK1AxJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Apr 13, 2016 at 8:38 AM, Oliver Kohll <oliver(at)agilechilli(dot)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.

http://www.postgresql.org/docs/9.5/interactive/functions-admin.html#FUNCTIONS-ADMIN-SET

​David J.​

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alex Ignatov 2016-04-13 17:14:23 Re: Freezing localtimestamp and other time function on some value
Previous Message Alex Ignatov 2016-04-13 15:40:29 Re: Freezing localtimestamp and other time function on some value