➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author malin
Recipients berker.peksag, erlendaasland, lemburg, malin, serhiy.storchaka
Date 2021-12-06.10:30:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1638786632.09.0.220750844955.issue44092@roundup.psfhosted.org>
In-reply-to
Content 
> How realistic is this scenario? If you compile with, for example 3.14.0 or
> newer, you'd link with sqlite3_trace_v2, not sqlite3_trace, so the loader
> would prevent you from running with anything pre 3.14. AFAIK, we've never
> had such problems.

I mean, after this change, different versions of SQLite will behave differently. And give a message for SQLITE_ABORT_ROLLBACK to explain this problem.

> It is a change of behaviour of the internal machinery. Does the change lead
> to wrong results (duplicate rows, wrong rows returned, no rows returned)?
> Corrupted/garbage data? Non-deterministic behaviour? Does any of the API's
> provided by sqlite3 not behave according to the documentation anymore?

It just leaks resource, apart from this, there seems to be no problem.
History
Date User Action Args
2021-12-06 10:30:32malinsetrecipients: + malin, lemburg, berker.peksag, serhiy.storchaka, erlendaasland
2021-12-06 10:30:32malinsetmessageid: <1638786632.09.0.220750844955.issue44092@roundup.psfhosted.org>
2021-12-06 10:30:32malinlinkissue44092 messages
2021-12-06 10:30:32malincreate