While using a database which supports rollback (mysql Innodb or Oracle), I can
do this in the same
transaction (autocommit is set to false):
. create an object A
. read back the object A with a pass-thru OQL query
. read back the object A with a db.load(...,objetA.getId())
. apply the rollback
I can't (before the rollback) :
. read back the object A with a OQL query like this
"select distinct dossier.idDossier from
cnam.scapin.metier.donnees.dossiers.Dossier dossier where nomPatronymique like
And If I have two different transactions before the rollback, I can't read
(anyway I use) in my transaction #2 the object being created in my transaction
#1. So the transaction isolation is ok.
I think there's really something wrong with the way the OQL query is executed
in this case. Is there something new on this point with the future version?
The same tests made using direct access by jdbc are ok.