Re: [HACKERS] [PATCHES] Values list-of-targetlists patch for comments (was Re:
От | David Fetter |
---|---|
Тема | Re: [HACKERS] [PATCHES] Values list-of-targetlists patch for comments (was Re: |
Дата | |
Msg-id | 20060809162242.GA19092@fetter.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] [PATCHES] Values list-of-targetlists patch for comments (was Re: (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: [HACKERS] [PATCHES] Values list-of-targetlists patch for comments (was Re:
|
Список | pgsql-docs |
On Wed, Aug 09, 2006 at 03:05:02PM +0200, Peter Eisentraut wrote: > Am Freitag, 4. August 2006 04:50 schrieb Tom Lane: > > I'd like to see us refactor the docs as necessary to reflect that > > idea. Peter is right that this needs some discussion in > > syntax.sgml as well as in the reference pages --- but I'm still > > not very clear on how the presentation should go. > > I'm beginning to think that VALUES might be a separate command after > all. What's below definitely bolsters that idea :) postgres=# VALUES(1); column1 --------- 1 (1 row) However, there are some oddities: postgres=# SELECT * FROM (VALUES (1,2)) AS foo(bar,baz); bar | baz -----+----- 1 | 2 (1 row) postgres=# (VALUES (1,2)) AS foo(bar,baz); ERROR: syntax error at or near "AS" LINE 1: (VALUES (1,2)) AS foo(bar,baz); Does the SQL standard have anything to say about assigning identifiers both to the entire VALUES() statement and to its columns when the VALUES() statement is by itself? Cheers, D -- David Fetter <david@fetter.org> http://fetter.org/ phone: +1 415 235 3778 AIM: dfetter666 Skype: davidfetter Remember to vote!
В списке pgsql-docs по дате отправления: