just found out the following:
A delete or a insert command, which effect more then one tuple/row, is transformed in several inserts or deletes on the table/index.
Each of theses inserts/deletes is put in a own transaction object to perform a rollback if necessary. The flag 'isNested' is false in these transaction (tx) objects. Theses tx are added to the list 'tTransaction' of the current session.
If you perfom an update, which usually results in several deletes and inserts on the table/index, there will be tx objects created too. However, in this case, the flag 'isNested' is set to true. Finally, the tx objects are added to the list 'tTransaction' in the current session to.
My questions:
- What's the difference between these tx objects.
- Why are not the tx objects with 'isNested == true' grouped in a parent transaction which represents the Update command. I think, it would be a good idea, wouldn't it?
Regards,
Daniel
P.S. Some classes in org.hsqldb have no visbility modifier like private or public, e.g. Database, Transaction.
Is there a reason for it or just forgotten? Anyway, I will and have to change it for my modifications.
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
