| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Sean Chittenden <sean(at)chittenden(dot)org>, Jon Jensen <jon(at)endpoint(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: massive quotes? |
| Date: | 2003-09-12 13:51:39 |
| Message-ID: | 10437.1063374699@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Note that there is no particular need to insist on any nearby newlines.
>> If the construct is written just following an identifier or keyword,
>> then you do need some intervening whitespace to keep the $Q$ from being
>> read as part of that identifier, but I doubt this will bother anyone.
>>
>> Note that I'm allowing only letters, not digits, in the string; this
>> avoids any possible ambiguity with $n parameter tokens. We have no
>> other SQL tokens that are allowed to start with $, so this creates no
>> other lexical ambiguity.
> Sounds interesting. So it is $$text$$ or $quote$text$quote$?
Either would work, yes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-09-12 13:53:10 | __cpu__ defines |
| Previous Message | Jan Wieck | 2003-09-12 13:51:38 | Re: Another small bug (pg_autovacuum) |