Skip site navigation (1) Skip section navigation (2)

RE: [INTERFACES] Re: [GENERAL] JDBC and insert - stack overflow

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
That's what I thought, but at that time in the morning, I wasn't sure

Peter T Mount, Enterprise Support
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
>> 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

Next:From: rjdDate: 1999-05-28 11:15:35
Previous:From: Tom LaneDate: 1999-05-27 21:37:52
Subject: Re: [INTERFACES] Wierd error when creating a table...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group