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

RE: Large Objects

From: "Dave Cramer" <Dave(at)micro-automation(dot)net>
To: <pgsql-jdbc(at)postgresql(dot)org>
Subject: RE: Large Objects
Date: 2001-07-29 20:37:54
Message-ID: 02cd01c1186e$586dbae0$8201a8c0@inspiron (view raw or flat)
Thread:
Lists: pgsql-jdbc
Yes, you have to commit the transaction at the end

Con.commit(), or con.rollback() I think.

Dave
-----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: July 29, 2001 4:20 PM
To: daniel(dot)fisher(at)vt(dot)edu
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] Large Objects 


Daniel Fisher <dfisher(at)vt(dot)edu> writes:
> I'm having some trouble inserting a large object into the database. 
> I'm fairly certain that the problem is in my java code because I wrote

> some quick PHP code and it worked fine. The main problem is I'm not 
> getting any errors, so I'm kinda stumped. The code appears to run 
> fine, but nothing is being inserted into the database.

The query trace shows that you are starting a transaction (with BEGIN)
and never committing it (no COMMIT or END).  So when you close the
connection, the transaction is rolled back, and its effects go away.

I suppose that having done "conn.setAutoCommit(false)", you need to add
a command to explicitly commit the transaction, but I don't know JDBC
well enough to know how you do that...

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster



In response to

pgsql-jdbc by date

Next:From: Kovács PéterDate: 2001-07-30 07:12:04
Subject: RE: Large Objects
Previous:From: Tom LaneDate: 2001-07-29 20:20:14
Subject: Re: Large Objects

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