This sounds like a classic case of something that should be a two-phase commit transaction performed atomically. The fact that it is not, and may even be spread across multiple processes, is a hole in DB consistency.
I do not think we want to get into doing *distributed* 2P transactions - I have worked on such things and they are a real bear. Non-distributed 2P transactions are much easier. Is there any thought to using the MariaDB fork of MySQL? Its Maria table engine is supposed to be a lot more reliable than MyISAM, and it has transaction semantics. Of course, MyISAM is still availble for those tables where transaction semantics is not needed. On Fri, 2009-07-31 at 15:32 +0100, Thomas Grimshaw wrote: > It's supposedly inserted into the region tables, but the issue comes > when the region server is unable to do this (or crashes), > the item is lost permanently. _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
