Received: from bush.rutgersinsurance.com (IDENT:root@rutgersinsurance.com [38.138.71.194]) by hub.org (8.10.1/8.10.1) with ESMTP id e7FGbGn48337 for ; Tue, 15 Aug 2000 12:37:17 -0400 (EDT) Received: from Adam ([10.10.10.51]) by bush.rutgersinsurance.com (8.9.3/8.9.3) with SMTP id MAA03053 for ; Tue, 15 Aug 2000 12:40:45 -0400 Message-ID: <00dd01c006d7$35a1b7e0$330a0a0a@Adam> From: "Adam Lang" To: References: Subject: Re: copy from Date: Tue, 15 Aug 2000 12:38:15 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200008/113 Hmmm... well, I don't think I have an "explicit" nextval. I created the table and then I did a create sequence broker_id; Are you implying that I can set the field to automatically create a nextval? Adam Lang Systems Engineer Rutgers Casualty Insurance Company ----- Original Message ----- From: "Stephan Szabo" To: "Adam Lang" Cc: Sent: Tuesday, August 15, 2000 12:34 PM Subject: Re: [SQL] copy from > Well, if you define your main table to have a serial, or an explicit > default nextval(seqid), you won't even need to do that. Just leave > the column off the insert list and the default should fill it for you. > > Stephan Szabo > sszabo@bigpanda.com > > On Tue, 15 Aug 2000, Adam Lang wrote: > > > I get it. I upload to the temp table, then for the select/insert I just do > > the nextval(seq_id) for the primary key field, correct?