| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] dollar quoting |
| Date: | 2004-02-15 16:42:40 |
| Message-ID: | 8642.1076863360@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> No, it won't. The problem is that it should, because the backend will
>> see that as '42' followed by a $foo$ quote start.
> Ok, I see what you are saying. This mismatch would only happen on
> invalid input, though. I believe that what I did will work on all legal
> input.
I'm unconvinced. Even if there are not any current syntaxes in which a
numeric literal can be adjacent to a string literal (I'm not totally
sure about that), what of the future? We should solve the problem
rather than assuming it won't bite us.
> I think that this might be cured by having psql recognise a legal
> identifier or keyword and eating it as a word, rather than treating it
> as just another set of bytes in the stream.
Hm, might work ... will think about it ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2004-02-15 17:13:58 | Re: RFC: Security documentation |
| Previous Message | Stephan Szabo | 2004-02-15 16:41:57 | Re: [SQL] 7.4 - FK constraint performance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2004-02-15 19:40:15 | Re: Afrikaans translation of libpq |
| Previous Message | Andrew Dunstan | 2004-02-15 14:36:58 | Re: [HACKERS] dollar quoting |