Managing long running transactions

[atlasphp]

Managing long running transactions

[pmjones]

Thank you for this cogent and valuable analysis. I can't do much about it yet, but I will ask you more about it when the time comes. Leaving open until then. In the mean time, please feel free to expand on your comments, or to submit PRs for review (cannot promise I will merge but I would like very much to see your ideas in code).

[jblotus]

Just wanted to add that implementing support for automatic nested transactions would also be useful. In the past I have needed smaller transactions deeper in the domain and not worrying about auto-committing the transaction you are inside of is handy.

[pmjones]

@jblotus Noted. Are you talking about actual SAVEPOINT implementation (for databases that support such) or just incrementing/decrementing a counter of how many times beginTransction() gets called?

[jblotus]

A counter - doctrine dbal has a good example of this approach including caveats =]
http://docs.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/transactions.html#transaction-nesting

[pmjones]

@jblotus Gotcha. I wonder if that's better as an Aura.Sql ExtendedPdo addition.

[pmjones]

@regilero @jblotus With this issue in mind, and because of other problems I discovered with Mapper::persist() not honoring transactions over multiple connections, I have started the 2.x branch, which uses a table-level ConnectionManager class. It can auto-open transactions as a connection is retrieved from the manager, return "write" connections in place of "read" ones while tables are writing, and so on. Cf. the 2.x changelog and the ConnectionManager class ...

• https://github.com/atlasphp/Atlas.Orm/blob/2.x/CHANGELOG.md
• https://github.com/atlasphp/Atlas.Orm/blob/2.x/src/Table/ConnectionManager.php

... and let me know what you think.

[djmattyg007]

This looks fantastic :)

[pmjones]

Closing due to lack of feedback (other than from @djmattyg007 -- thanks!). Please comment here if you find a reason to reopen it.