Re: Insert more than one t-uple in a single sql - Mailing list pgsql-general

From David Fetter
Subject Re: Insert more than one t-uple in a single sql
Date
Msg-id 20060210011157.GC15836@fetter.org
Whole thread Raw
In response to Re: Insert more than one t-uple in a single sql  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Insert more than one t-uple in a single sql  ("Silas Justiniano" <silasju@gmail.com>)
List pgsql-general
On Thu, Feb 09, 2006 at 07:12:45PM -0500, Tom Lane wrote:
> >> You can't do that in postgres, sorry. That's a mysql-ism.
> >>
> >> Gonzalo Villegas wrote:
> >>
> >>> It must be something like
> >>> insert into table (field1,field2,...) values (v1,v2,...),(b1,b2,...),
> >>> (c1,c2,...)
>
> Actually, that's not a mysql-ism, it's SQL-spec syntax.  We haven't
> got round to implementing it, partly because the SELECT ... UNION
> ALL ...  syntax provides a perfectly good substitute.  It is on the
> TODO list though.

Another way it's different from COPY is that the VALUES can take
expressions.

What all would need to change in order to implement this?  There
appear to be things in src/backend/parser and src/bin/psql that bear
on this.  Would libpq and ecpg need to change?

Cheers,
D
--
David Fetter david@fetter.org http://fetter.org/
phone: +1 415 235 3778

Remember to vote!

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: distinct not working in a multiple join
Next
From: David Rio Deiros
Date:
Subject: Re: distinct not working in a multiple join