From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Rafael Azevedo" <rafael(at)webpro(dot)com(dot)br> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: feature suggestion |
Date: | 2007-08-01 03:13:15 |
Message-ID: | b42b73150707312013o6df39a2apb860b82afe90b098@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/1/07, Rafael Azevedo <rafael(at)webpro(dot)com(dot)br> wrote:
> Imagine that you have about 30 fields.
> Ok, then your first SQL is done.
> Now, you just have to add 10 more fields.
> Its very easy to get lost. If we have this implementation, you could just
> add
>
> Field31 = 'text',
> Field32 = 'text'
I have to admit this syntax has a lot of advantages over the
insert...values statement, especially in dynamic sql situations. That
being said, more and more I just write queries insert..select which
would be an awkward fit. mysql compatibility is usually pretty poor
justification of a feature (they have a million ways to do everything)
and things have to stand on general merit.
It is really quite unfortunate the way certain aspects of the sql
standard evolved (indirectly causing these types of issues) but that
is a topic for another day :)
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Rafael Azevedo | 2007-08-01 03:13:57 | Re: feature suggestion |
Previous Message | Alvaro Herrera | 2007-08-01 03:00:53 | GIT patch |