hi thanks for your answer.
i m trying to make sense of this, because that particular part of the
code is something like this
try
session.save(something);
catch
session.update(something);
...
and i get the error for the update
Hi!
> i m trying to make sense of this, because that particular part of the
> code is something like this
[quoted text clipped - 4 lines]
> session.update(something);
> ...
Hmm... Two possibilities come to my mind:
Firstly, what exactly are you catching? Could it be that the
try-block throws something outside the save()-method? In a case like
this, the save() would actually have completed before the
catch-block was invoked.
Secondly, could it be that your database does not support
transactions or is set to a wrong transaction isolation level?
If you were using MySQL with myISAM tables (which do not support
transactions), part of the save() operation could actually be
completed before exception is thrown. Missing transaction support,
these updates would be persistent and would be seen by the update().
HTH,
Phil
Jo - 08 May 2007 16:19 GMT
hi,
the first option no idea. however i added a line to write to the log
in the case there is an exception
second option, I m using MS SQL, and i m not sure what you mean by
transactions, can you please point me to somwhere i can read more
abotu this?
I googled java transaction MS SQL and i get some info regarding the
JDB driver for Ms sql 2005, no info on the 2k version
Cheers
j
> Hi!
>
[quoted text clipped - 26 lines]
>
> Phil