Context Navigation

Changes between Initial Version and Version 1 of Ticket #2227, comment 27

-              initial
+              v1
 I agree that nested calls to transaction management commands should transparent start using savepoints. It seems like the obvious abstraction layer.
+I agree that nested calls to transaction management commands should transparently start using savepoints. It seems like the obvious abstraction layer.
 However, for backends which do not support savepoints, what would the fallback be? The only thing I can think of is to check for nesting and only allow transactions to commit in the outer nested block. This means that different backends will behave very differently, massively breaking the abstraction.
+For backwards compatibility, the current transaction handling methods will probably have to stay, as they provide a 'broken', yet consistent way of handling transactions between backends. There are workarounds for core framework features, such as #15694. However, a new set of decorators with a slightly different API could be provided in parallel, with a signature something like this:
+For backwards compatibility, the current transaction handling methods will probably have to stay, as they provide a 'broken', yet consistent way of handling transactions between backends. There are workarounds for core framework features, such as #15694.
+However, a new set of decorators with a slightly different API could be provided in parallel, with a signature something like this:
 {{{