Changes between Initial Version and Version 1 of Ticket #37369, comment 7
- Timestamp:
- Sep 28, 2026, 8:08:08 AM (2 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #37369, comment 7
initial v1 1 Introducing a new `after_commit_else_immediate()` API seems reasonable to me, if the dangers are clearly documented. It is significantly better than introducing an `actually_don't_defer=` option to the existing API, and is at least clear to callers that their code is expected to handle being called both in and out of a transaction. (I don't think it's a good idea to write code like that, but I understand that I'm stricter on that issue than many others might choose to be.)1 Introducing a new `after_commit_else_immediate()` (or whatever) API seems reasonable to me, if the dangers are clearly documented. It is significantly better than introducing an `actually_don't_defer=` option to the existing API, and is at least clear to callers that their code is expected to handle being called both in and out of a transaction. (I don't think it's a good idea to write code like that, but I understand that I'm stricter on that issue than many others might choose to be.)