diff options
author | R David Murray <rdmurray@bitdance.com> | 2013-01-10 16:13:34 (GMT) |
---|---|---|
committer | R David Murray <rdmurray@bitdance.com> | 2013-01-10 16:13:34 (GMT) |
commit | 7bd04867e53d78ddb0f5e8f78b9256298d41fadd (patch) | |
tree | c6d529a2ceb6a8ec7335f74d53f8d20af6629e4f /Misc | |
parent | 8eee081d4041a59b3c8088cba8dcaafc22a88c00 (diff) | |
parent | b52312923bee35b86fc072ec546cc3e588ae64c9 (diff) | |
download | cpython-7bd04867e53d78ddb0f5e8f78b9256298d41fadd.zip cpython-7bd04867e53d78ddb0f5e8f78b9256298d41fadd.tar.gz cpython-7bd04867e53d78ddb0f5e8f78b9256298d41fadd.tar.bz2 |
merge #15545: fix sqlite3.iterdump regression on unsortable row_factory objects.
The fix for issue 9750 introduced a regression by sorting the row objects
returned by fetchall. But if a row_factory such as sqlite3.Row is used, the
rows may not be sortable (in Python3), which leads to an exception. The
sorting is still a nice idea, so the patch moves the sort into the sql.
Fix and test by Peter Otten.
Diffstat (limited to 'Misc')
-rw-r--r-- | Misc/NEWS | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -142,6 +142,10 @@ Core and Builtins Library ------- +- Issue #15545: Fix regression in sqlite3's iterdump method where it was + failing if the connection used a row factory (such as sqlite3.Row) that + produced unsortable objects. (Regression was introduced by fix for 9750). + - Issue #16491: IDLE now prints chained exception tracebacks. - Issue #15972: Fix error messages when os functions expecting a file name or |