From: Paul Friberg CEO - ISTI <p.friberg@isti.com>
To: pgsql-sql@postgresql.org
To: pgsql-hackers@postgresql.org
Subject: PostgreSQL COPY command
Date: Mon, 19 Oct 1998 09:03:39 -0400
Message-ID: <362B38AB.BCFFE717@isti.com> (raw)
Hi all,
Does anyone know if there are plans to upgrade the
COPY command so it spits back some intelligent results
when it finishes. At the present time if it finds a bad
row or a non-unique key set, it simply quits out with a
statement:
"resetting connection"
Which is not very informative. Let me know if this part of
the code needs working on. If nobody else is adding this,
I would be happy to dive in.
I could imagine this spitting out a message about a certain
line not passing muster, or even the total number of rows
in the file input/output being listed (as is now returned
with the INSERT/DELETE/UPDATE/SELECT commands).
Cheers,
Paul
--
Paul Friberg - p.friberg@isti.com - http://www.isti.com
(914) 256-9290 Office - (914) 256-9299 FAX
ISTI==Instrumental Software Technologies, Inc.
Systems Integration and Software Development Specialists
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-hackers@postgresql.org
Cc: p.friberg@isti.com, pgsql-sql@postgresql.org
Subject: Re: PostgreSQL COPY command
In-Reply-To: <362B38AB.BCFFE717@isti.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