Thanks...
--
--
Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist
http://www.denninger.net Tired of spam at your company? LOOK HERE!
http://childrens-justice.org Working for family and children's rights
http://diversunion.org LOG IN AND GET YOUR TANK STICKERS TODAY!
http://scubaforum.org Come talk about DIVING!
On Tue, Feb 17, 2004 at 08:29:06AM -0800, Stephan Szabo wrote:
> [EMAIL PROTECTED]
>
> On Tue, 17 Feb 2004, Karl Denninger wrote:
>
> > I want to insert values from one table into another, and add some "default"
> > values (that are not defaults on the table different reasons - that is, this
> > is maintenance function and in normal operation there would be "real" values
> > there - and null is valid)
> >
> > So, I want to do, for example, the following:
> >
> > insert into table (id, time, type) values (select id, now(), '1' from secondtable);
> >
> > Postgres's command line pukes on this, complaining that "select" is invalid
> > inside the values part of the definition.
> >
> > SQL's language specification says otherwise, as does "\h insert" from the
> > command line.
>
> I think what you want is
> insert into table (id, time, type) select id, now(), '1' from secondtable;
>
> The choices allowed right now are default values, something that is
> basically a row constructor with values [*] or a query.
>
> [*] - The full spec allows a list of row constructors but we don't
> currently.
>
>
>
> %SPAMBLOCK-SYS: Matched [EMAIL PROTECTED], message ok
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
