On Mon, Dec 10, 2007 at 08:13:09PM +0100, Thomas Carsten Franke wrote: > If I do so I get following error by Postgres: > > org.postgresql.util.PSQLException: ERROR: current transaction is > aborted, commands ignored until end of transaction block It means exactly what it says. You (or Java for you) started a transaction block and everything in a transaction block is either committed or aborted. Once an error has been raised, everything after that is ignore till the end of the transaction. > To work around this I add an dbCon.rollBack() after select statement > above in good and in bad times. After that ALTER works. > Can someone explain me why I need this rollback ? Rollback/commit either will do. You just need ot start a new transaction. What people usually do is to do stuff like what you're doing outside any transactions, thus avoiding the whole problem. Have a nice day, -- Martijn van Oosterhout <kleptog@xxxxxxxxx> http://svana.org/kleptog/ > Those who make peaceful revolution impossible will make violent revolution inevitable. > -- John F Kennedy
Attachment:
signature.asc
Description: Digital signature
