From: Josh Berkus <josh@agliodbs.com>
To: Herb Blacker <hhb@isgenesis.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: [NOVICE] Loading current_user and current_timestamp using COPY
Date: Wed, 10 Oct 2001 21:20:12 -0700
Message-ID: <web-145846@davinci.ethosmedia.com> (raw)
In-Reply-To: <200110110102.f9B126k26142@www.isgenesis.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, hhb@isgenesis.com
Subject: Re: [NOVICE] Loading current_user and current_timestamp using COPY
In-Reply-To: <web-145846@davinci.ethosmedia.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox