- Issue created by @mondrake
- 🇺🇸United States mfb San Francisco
For inspiration see https://github.com/laravel/framework/tree/10.x/src/Illuminate/Database/E...
- Assigned to mondrake
- Merge request !4682Issue #3348590: Add transaction-related events to the Database API → (Open) created by mondrake
- last update
about 1 year ago Custom Commands Failed - Issue was unassigned.
- Status changed to Needs review
about 1 year ago 10:53am 1 September 2023 - 🇮🇹Italy mondrake 🇮🇹
Started something, fit nicely with latest improvements in 📌 Refactor transactions Fixed . Looking forward to an early review - this sets the basis, more events are just more meat around this bone.
- last update
about 1 year ago 30,136 pass - Status changed to Postponed
about 1 year ago 7:47am 4 September 2023 - 🇮🇹Italy mondrake 🇮🇹
Postponed on 🐛 Strengthen TransactionManager Needs work
- Status changed to Needs work
about 1 year ago 8:48am 14 September 2023 - Status changed to Postponed
8 months ago 10:11pm 19 March 2024 - 🇮🇹Italy mondrake 🇮🇹
We cannot do this now, 🐛 Transaction autocommit during shutdown relies on unreliable object destruction order (xdebug 3.3+ enabled) Needs review introduced
Database::commitAllOnShutdown()
which runs at a time when the event dispatcher has been destroyed already, so events fail. One more reason to move towards explicit commit. - 🇺🇸United States mfb San Francisco
eesh, seems not-ideal to wait until most-everything is destroyed to commit transactions, i.e. difficult to respond to various transaction commit failure modes.