@BenMorel yes kind of. The question is if we should not rather be agnostic about the transaction managers current state (how many transactions are active/nested etc.) and have a `$txm->getTransaction($definition)` instead of `$txm->createTransaction($definition)`. So we are just asking the transaction manager to provide an appropriate transaction according to the given specifications. I think this could ease up the usage when you don't know the current state of the transaction manager and its attached transactions. You basically just tell it to give you a transaction that fits your needs and the manager is doing the rest internally (like suspending active transactions, commiting transaction before creating a new one etc.). Of course this is a little theoretical atm but I definitely like the idea.
This could open up features in ORM where you could annotate certain methods with `@Transactional(REQUIRED)` or similar to control transactional operation entity-wise (maybe).