От: Harald Fuchs
Тема: Re: COPY vs INSERT
Дата: ,
Msg-id: puu0lg4sc0.fsf@srv.protecting.net
(см: обсуждение, исходный текст)
Ответ на: Re: COPY vs INSERT  ("Jim C. Nasby")
Список: pgsql-performance

Скрыть дерево обсуждения

 (Steven Rosenstein, )
 Re:  (Tom Lane, )
  Re: COPY vs INSERT  (Mischa Sandberg, )
   Re: COPY vs INSERT  ("David Roussel", )
    Re: COPY vs INSERT  (Mischa Sandberg, )
     Re: COPY vs INSERT  (Christopher Petrilli, )
      Re: COPY vs INSERT  (Keith Worthington, )
     Re: COPY vs INSERT  (Kris Jurka, )
      Re: COPY vs INSERT  (Mischa Sandberg, )
       Re: COPY vs INSERT  (Kris Jurka, )
    Re: COPY vs INSERT  (John A Meinel, )
    Re: COPY vs INSERT  (Christopher Kings-Lynne, )
     Re: COPY vs INSERT  (Tom Lane, )
      Re: COPY vs INSERT  ("Jim C. Nasby", )
       Re: COPY vs INSERT  (Dennis Bjorklund, )
        Re: COPY vs INSERT  ("Jim C. Nasby", )
       Re: COPY vs INSERT  (Harald Fuchs, )
       Re: COPY vs INSERT  (Bruno Wolff III, )
        Re: COPY vs INSERT  (Tom Lane, )
  Re:  (Mike Rylander, )

In article <>,
Dennis Bjorklund <> 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 ;-)


В списке pgsql-performance по дате сообщения:

От: Tom Lane
Дата:
Сообщение: Re: Bad choice of query plan from PG 7.3.6 to PG 7.3.9
От: Rosser Schwarz
Дата:
Сообщение: Re: [SQL] ORDER BY Optimization