Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9B4KFn37644 for ; Thu, 11 Oct 2001 00:20:15 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 145846; Wed, 10 Oct 2001 21:20:12 -0700 From: "Josh Berkus" Subject: Re: [NOVICE] Loading current_user and current_timestamp using COPY To: "Herb Blacker" Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Wed, 10 Oct 2001 21:20:12 -0700 Message-ID: In-Reply-To: <200110110102.f9B126k26142@www.isgenesis.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_===145846====davinci.ethosmedia.com===_" X-Archive-Number: 200110/144 X-Sequence-Number: 5099 This is a multi-part MIME message --_===145846====davinci.ethosmedia.com===_ Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Herb, > Right now I'm loading 1,500 test records in my largest table...but I > don't > want to do inserts...I'll stay with COPY and ignore the NULLS for > now. > In the future, however, I could be bulk loading up to 60,000 records. > Of course, all records after that will be inserts, so perhaps the > point is > moot. Although...if COPY can handle the now() function, it should be > able > to handle the current_user/current_timestamp without too much > overhead. > Well....thanks for the help Sorry I couldn't be more help. I haven't seen any answers on the SQL list. I can think of several workarounds, depending on what kind of a user interface you're using, such as having a linked batches table. -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco --_===145846====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===145846====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===145846====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===145846====davinci.ethosmedia.com===_--