From: | Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Mount (Home)" <peter(at)retep(dot)org(dot)uk> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | RE: [INTERFACES] Re: [GENERAL] JDBC and insert - stack overflow |
Date: | 1999-05-28 09:17:31 |
Message-ID: | A9DCBD548069D211924000C00D001C44281D6D@exchange.maidstone.gov.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
That's what I thought, but at that time in the morning, I wasn't sure
;-)
--
Peter T Mount, Enterprise Support
petermount(at)it(dot)maidstone(dot)gov(dot)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(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, May 27, 1999 9:45 PM
To: Peter T Mount
Cc: pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] Re: [GENERAL] JDBC and insert - stack overflow
Peter T Mount <peter(at)retep(dot)org(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | rjd | 1999-05-28 11:15:35 | |
Previous Message | Tom Lane | 1999-05-27 21:37:52 | Re: [INTERFACES] Wierd error when creating a table... |