Re: SET TRANSACTION must be first statement of transaction -- the real cause

Hi Raphael, can you please open a scarab Bug report on this ? http://issues.apache.org/scarab/issues Just to make sure that it is not forgotten. (I'd like to look into this, but I do not have the time at the moment) Thanks, Thomas [EMAIL PROTECTED] schrieb am 24.01.2005 17:40:43:

Re: SET TRANSACTION must be first statement of transaction -- the real cause

Thre real cause of the problem turned out to be something silly that I had done. I had done a save() on a newly created object and then also done a doInsert(), afterthe PK had already been filled in. The doInsert() did NOT throw an exception or return any sort of an error. The Oracle error