From: | Harald Fuchs <use_reply_to(at)protecting(dot)net> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: COPY vs INSERT |
Date: | 2005-05-06 09:27:43 |
Message-ID: | puu0lg4sc0.fsf@srv.protecting.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
In article <Pine(dot)LNX(dot)4(dot)44(dot)0505060927520(dot)7072-100000(at)zigo(dot)dhs(dot)org>,
Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> writes:
> On Fri, 6 May 2005, Jim C. Nasby wrote:
>> Has thought been given to supporting inserting multiple rows in a single
>> insert? DB2 supported:
>>
>> INSERT INTO table VALUES(
>> (1,2,3),
>> (4,5,6),
>> (7,8,9)
>> );
>>
>> I'm not sure how standard that is or if other databases support it.
> The sql standard include this, except that you can not have the outer ().
> So it should be
> INSERT INTO table VALUES
> (1,2,3),
> (4,5,6),
> (7,8,9);
Since MySQL has benn supporting this idiom for ages, it can't be
standard ;-)
From | Date | Subject | |
---|---|---|---|
Next Message | Jona | 2005-05-06 11:14:51 | Re: Bad choice of query plan from PG 7.3.6 to PG 7.3.9 |
Previous Message | Christopher Kings-Lynne | 2005-05-06 08:41:02 | Re: Bad choice of query plan from PG 7.3.6 to PG 7.3.9 |