| From: | Oliver Kohll <oliver(at)agilechilli(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | SET prepared statement |
| Date: | 2016-04-13 15:38:28 |
| Message-ID: | D2A07336-827A-4F1B-938B-7FFF4F804F59@agilechilli.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 <https://wiki.postgresql.org/wiki/Todo>
Oliver
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Ignatov | 2016-04-13 15:40:29 | Re: Freezing localtimestamp and other time function on some value |
| Previous Message | Feld, Michael (IMS) | 2016-04-13 15:32:23 | Re: pg_upgrade error regarding hstore operator |