| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Herb Blacker" <hhb(at)isgenesis(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: [NOVICE] Loading current_user and current_timestamp using COPY |
| Date: | 2001-10-11 04:20:12 |
| Message-ID: | web-145846@davinci.ethosmedia.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/plain | 2 bytes |
| unknown_filename | text/plain | 2 bytes |
| unknown_filename | text/plain | 2 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-10-11 05:11:06 | Re: [NOVICE] Loading current_user and current_timestamp using COPY |
| Previous Message | Stephan Szabo | 2001-10-11 00:18:25 | Re: VARCHAR vs TEXT |