RE: [INTERFACES] Re: [GENERAL] JDBC and insert - stack overflow - Mailing list pgsql-interfaces

From Peter Mount
Subject RE: [INTERFACES] Re: [GENERAL] JDBC and insert - stack overflow
Date
Msg-id A9DCBD548069D211924000C00D001C44281D6D@exchange.maidstone.gov.uk
Whole thread Raw
List pgsql-interfaces
That's what I thought, but at that time in the morning, I wasn't sure
;-)

--
Peter T Mount, Enterprise Support
petermount@it.maidstone.gov.uk
Anything I write here are my own views, and cannot be taken as the
official words of Maidstone Borough Council

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Thursday, May 27, 1999 9:45 PM
To: Peter T Mount
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Re: [GENERAL] JDBC and insert - stack overflow



Peter T Mount <peter@retep.org.uk> writes:
>> By the way, use con.setAutoCommit( false ) to have all the inserts in
one
>> big transaction. It saves a lot of time.

> Don't forget to commit() at the end, as you can't guarantee that a
> transaction will be committed when the connection closes.

In fact, I believe that we guarantee the opposite: any open transaction
will be aborted if the client closes the connection without sending a
commit command...
        regards, tom lane


pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: [INTERFACES] Wierd error when creating a table...
Next
From: rjd@intekom.co.za
Date:
Subject: