Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3HKdEu37192 for ; Tue, 17 Apr 2001 16:39:14 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f3HKcsR06161; Tue, 17 Apr 2001 16:38:54 -0400 (EDT) To: clayton cottingham cc: pgsql-sql@postgresql.org Subject: Re: is this proper sql? In-reply-to: <3ADC9EB4.C8E80451@smartt.com> References: <3ADC9EB4.C8E80451@smartt.com> Comments: In-reply-to clayton cottingham message dated "Tue, 17 Apr 2001 12:51:16 -0700" Date: Tue, 17 Apr 2001 16:38:53 -0400 Message-ID: <6157.987539933@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/282 X-Sequence-Number: 2637 clayton cottingham writes: > hi one of the developers here at work say this should work > insert into detail (det_id,det_mas_id,det_date,det_amt) values > (0,0,now(),'0'), (1,1,now(),'1'); Multiple rows in INSERT ... VALUES are legal according to the SQL92 spec, but we don't support that (yet). regards, tom lane