Message414793
Ah, one of my very first contributions, bpo-40318, comes back to haunt me:
In bpo-40318, we migrated from the old SQLite trace API (sqlite3_trace) to SQLite trace v2 API (sqlite3_trace_v2). GH-19581, which introduced this change, introduced a bug: the old trace API _implicitly_ expanded bound parameters; the new trace API does not. However, there was no tests for this behaviour, so the regression was unnoticed[^1].
So, this bpo is actually a bug fix; not a feature. It should be backported to 3.10, which contains the regression.
I'm preparing a fix for GH-28240, and I'll prepare a 3.10 backport including both GH-2840 and its upcoming fix.
[^1]: There has been no bug reports regarding this change in behaviour, so it seems to have gone under most people's radar. |
|
Date |
User |
Action |
Args |
2022-03-09 11:14:46 | erlendaasland | set | recipients:
+ erlendaasland, JelleZijlstra |
2022-03-09 11:14:46 | erlendaasland | set | messageid: <1646824486.18.0.958860008413.issue45138@roundup.psfhosted.org> |
2022-03-09 11:14:46 | erlendaasland | link | issue45138 messages |
2022-03-09 11:14:46 | erlendaasland | create | |
|