From: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
---|---|
To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: INSERT ... ON CONFLICT syntax issues |
Date: | 2015-05-08 09:06:53 |
Message-ID: | CAEzk6ffE_hsyunJaknFLU5gV--whBVESJj4pu_V8bAk_U-MVRw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7 May 2015 at 18:37, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I don't see a problem at all, with one exception: If we want the AS to
> be optional like in a bunch of other places, we have to either promote
> VALUES to a reserved keyword, only accept unreserved keywords, or play
> precedence games. I think it'd be perfectly fine to not make AS
> optional.
>
Although I've always used "AS"
in all contexts
because I think the language is
horribly
unclear without it, it seems obtuse to
allow its absence
in the SQL-conforming parts of the language and not
elsewhere
.
Is anyone really using VALUES as a non-keyword? It's reserved in all the
SQL standards, which seems like storing up trouble for anyone using it
otherwise.
Geoff
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-05-08 11:15:58 | Re: Obsolete mention of src/tools/backend |
Previous Message | Fabien COELHO | 2015-05-08 09:02:16 | Re: commitfest app bug/feature |