I'm not saying we have any such code, I'm asking what to do when one wants to introduce such code. It's entirely feasible some new functionality requires serializable transactions, so we might want to keep that into consideration.
Sent from my Android phone. On 24 Aug 2012 00:30, "Platonides" <[email protected]> wrote: > On 23/08/12 23:54, Jeroen De Dauw wrote: > > Hey, > > > > One concern I have with big transcations that have lots of stuff in them > is > > that some code might get called in which needs to run in a transaction > with > > a higher isolation level then the current one. For MySQLs InnoDB the > > default is repeatable read, so if you have code that requires > > serializability and gets called during that transaction, you're basically > > fucked. Or am I missing something? > > > > Cheers > > I don't think we have any code requiring a different transaction isolation. > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
