Pedro, Nested transactions are new fairly recently to many databases, including Postgresql. Not many applications have even been designed to use them. And yes MySQL does not yet support nesting and therefore closing the previous transaction when issuing a START TRANSACTION is the right behavior. And I have never seen the behavior of the CHECK clause on the CREATE TABLE be an issue. If it was there would be all kinds of articles in the trade journals. As you pointed out we are now talking about the different 'personalities' of various databases. But even with some of these personality differences there is no way that the architecture of Tiny which is really rather simple in comparison to most is going to get in the way of an implementation for MySQL unless someone intentionally makes a very rigid non-flexible design and Tiny has been everything about flexibility so I do not think this will be the case.
Gerry _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
