Re: Another nut to crack with insertion into tables... *sigh*

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Gemeinschaft Studienarbeit Datenbanken" <oodbms(at)floppy(dot)org>
Cc: pgsql-sql(at)hub(dot)org
Subject: Re: Another nut to crack with insertion into tables... *sigh*
Date: 1998-09-28 14:02:10
Message-ID: 20074.906991330@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

I dunno about arrays, but this one I think I can answer:

> insert into Rollenspiel
> (Name, HerstellerID, Erscheinungsdatum,
> Bestellnummer, Preisempfehlung,
> Beschreibung,
> Computertyp, Datentraegertyp,
> System, AnzahlCharaktere, Typ,
> Cluebook, SpielstandEditor)
> values
> ('Might & Magic I', (select HerstellerNummer from Hersteller
> where Name like '%Blueborg%'), '17.03.1986',
> 'role01', '29,50',
> '{"Einfach irgendeine Beschreibung halt..."}',
> '{"PC", "Mac", "c64", "Atari"}', '{"Diskette", "CD"}',
> 'Freies System', 6, 'Fantasy',
> '{"Solution to Might & Magic Series", "The Might & Magic I Solution"}',
> '{"http://www.mightandmagic.de/I/editors.html"}');
> ERROR: parser: parse error at or near "select"

I believe sub-selects are currently only supported in WHERE clauses.
Supporting them elsewhere is on the TODO list for a future release
(no, 6.4 won't have it). In the meantime you'll have to read back
the result of the sub-select and include it in the text of the INSERT.

(I'm not sure whether the SQL spec allows a select in an INSERT like this
anyway. What happens if the sub-select returns no tuples, or more than
one tuple?)

regards, tom lane

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Bryan White 1998-09-28 14:50:27 Setting current time on insert
Previous Message Sferacarta Software 1998-09-28 13:35:27 Re: [SQL] Another nut to crack with insertion into tables... *sigh*