Looking into OJB implemenations, it seems that deletePersistent use the transaction of the current thread. So ok for the SQL transaction sequence, sorry for asking in last mail. I was confused between DB.deletePersistent(o), ExtTx.markDelete(o), and ExtTx.deletePersistent(o) methods. It seems all do the same.
I can't get rid of those dead lock, occurring when update/delete object in complex and different transactions. Do i have to lock objects to be deleted to avoid concurrent updating transaction (plausibly locking DB records) ? Does someone use such a technique ? Thanks for help. On 12/8/06, Bruno CROS <[EMAIL PROTECTED]> wrote:
Hi, Just one question. Using ODMG, if deletePersistent(o) is called from the Impl.getDatabase(), how "SQL DELETE" query post can be done with the other "INSERT/UPDATE" in the same SQL transaction without refering THE transaction? Why ODMG delete object tutorial talk about deletePersitent way, whereas ExtTx.markDelete(o) would be more appropriate considering SQL queries sequence in transaction? Need help. Regards. Bruno
