problems with currval and rollback

From: Assad Jarrahian <jarraa(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: problems with currval and rollback
Date: 2005-12-23 00:25:14
Message-ID: 4bd3e1480512221625q71115ffer4e5b0e9b10f84b17@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,
So I started to make some changes with my code here and there
(nothing to do with the relevant lines) and suddenly currval and
rollback don't work.

try{
db.setAutoCommit(false);
addLM.setInt(1, lm.getOrigin());
.......
addLM.executeUpdate();
sql = db.createStatement();
ResultSet result = sql.executeQuery("SELECT
currval('lm_id_seq');");
if (result. next()){
db.commit();
db.setAutoCommit(true);
else{
db.rollback(); //reverse all changes
db.setAutoCommit(true);
}
catch(SQLException ex){
try {
db.rollback();
db.setAutoCommit(true);
} catch (SQLException e) {
throw e;
}
throw ex;
}

What happens is that the it inserts a db, but cannot get a value back
using currval (ERROR: ERROR: currval of sequence "lm_id_seq" is not
yet defined in this session 55000 ) , yet the db gets the addlm
inserted.

Shouldn't it rollback?
Furthermore, why would currval suddenly stop working?

Much thanks for your feedback in advance.

-assad

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2005-12-23 00:30:40 Re: problems with currval and rollback
Previous Message Trent Shipley 2005-12-23 00:05:49 Re: Inheritance Algebra