Hello Here is some proof of concept code to allow nested transactions: http://gist.github.com/324022
It needs to modify the Transaction internals and DataObjectAdapter API - I suspect perhaps a neater way is to just pass the depth through to the data object adapter and it can select the correct primitive. This way SQL Server can just always return the normal one, PG/MySQL can return nested primitive when depth > 0. Also adds a new transaction primitive to data_objects, but I don't think this is a big deal. Thoughts? Xav -- You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.
