I would second this motion as it relates to bulk inserts, I also love
PG, but it's bulk insert/copy from file routines are definitely one area
where it cannot claim to be "most advanced".
My own wish list includes :
*Copy to a new table - so that a table in the db is created - default is
for al
On Sat, Nov 27, 2004 at 11:37:34AM +0200, Victor Ciurus wrote:
> And how does exactly PG8.0 help us with this?
You can use BEGIN ... EXCEPTION ... END blocks. It doesn't help you
with COPY/IGNORE ON DUPLICATES though.
> Tom, coould you be so kind and tell me/us when will PG incorporate
> such a
Am Fr, den 26.11.2004 schrieb diya das um 14:28:
> I am just a beginner in postgreSQL and writing some
> functions in PL/pgSQL. I use the libpq interface in
> the client to call this funtions. My pgsql function
> does an insert to a table and I have opened a
> transaction block before calling my
And how does exactly PG8.0 help us with this?
Tom, coould you be so kind and tell me/us when will PG incorporate
such a hugely claimed feature like "copy table_x from 'file_y.txt'
(using delimiters) IGNORE ON DUPLICATES"?
I do LOVE PG and I'm very pleased with its overall features level
still the
diya das <[EMAIL PROTECTED]> writes:
> My pgsql function
> does an insert to a table and I have opened a
> transaction block before calling my function from the
> client. When the insert operation fails due to unique
> key violation the whole transaction aborts. Is there a
> way I can handle this e
Hi,
I am just a beginner in postgreSQL and writing some
functions in PL/pgSQL. I use the libpq interface in
the client to call this funtions. My pgsql function
does an insert to a table and I have opened a
transaction block before calling my function from the
client. When the insert operation f
