| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql feature thought |
| Date: | 2006-05-16 13:25:52 |
| Message-ID: | 11426.1147785952@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Glaesemann <grzm(at)seespotcode(dot)net> writes:
> On May 16, 2006, at 14:17 , Tom Lane wrote:
>> [1] Mostly. There's the infamous continued-string-literal
>> construct...
> Are you referring to this?
> ^
> test=# SELECT 'foo'
> test-# 'bar'; -- valid
Yeah. It seems weird that a newline should be *required* there.
I think I understand why the SQL committee did that: they thought
SELECT 'a' 'b'
was much too likely to be a syntax error and shouldn't be made into
a valid construct. But it's weird nonetheless, and awkward to
implement.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-16 13:31:42 | Re: Creating a Pseudocolumn |
| Previous Message | Pavel Stehule | 2006-05-16 13:13:24 | Re: Wrong plan for simple join with index on FK |