| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: info about patch: using parametrised query in psql |
| Date: | 2009-12-25 17:26:44 |
| Message-ID: | 6344.1261762004@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I think maybe what we need here is a piece of syntax to indicate that a
> specific parameter should be substituted after first being passed
> through PQescapeStringConn.
I agree that a global flag that changes the behavior of :foo is a
seriously bad idea. Alternate syntax would be much better, but how
exactly can we shoehorn that in? Maybe something like
:!foo
ie put some non-letter flags between the : and the variable name.
It would obviously not work to use ::foo, but I think many other
punctuation characters would be safe (would not conflict with any
likely SQL usage). We could have a couple of different flags to
signal whether you want single or double quoting of the variable
value.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-12-25 17:54:13 | Re: Initial refactoring of plperl.c - rebased [PATCH] |
| Previous Message | Matteo Beccati | 2009-12-25 17:12:51 | PQescapeByteaConn and the new hex encoding |