Message393944
The effect of PR 26026 is that InterfaceError is no longer raised for fetch across rollback; instead it is up to SQLite how to handle this:
- for some cases, SQLITE_ABORT or SQLITE_ABORT_ROLLBACK may be returned, which will result in an OperationalError (accompanied by a nice error message provided by SQLite)
- for other cases, no error is returned; the operation is allowed and succeeds as expected
- for yet other cases, no error is returned, and the operation was rolled back
A NEWS entry should mention the change in behaviour, but I can't see how it would break existing projects; the current code disallows fetch across rollback (InterfaceError), so any problematic code would have been found, handled and fixed during debugging. |
|
Date |
User |
Action |
Args |
2021-05-19 10:25:11 | erlendaasland | set | recipients:
+ erlendaasland, lemburg, berker.peksag, serhiy.storchaka |
2021-05-19 10:25:11 | erlendaasland | set | messageid: <1621419911.77.0.983955793963.issue44092@roundup.psfhosted.org> |
2021-05-19 10:25:11 | erlendaasland | link | issue44092 messages |
2021-05-19 10:25:11 | erlendaasland | create | |
|