| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | gh-79009: sqlite3.iterdump now correctly handles tables with autoincrement ↵ | Miss Islington (bot) | 2022-06-19 | 1 | -1/+13 |
| | | | | | | | | | (GH-9621) Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com> (cherry picked from commit affa9f22cfd1e83a5fb413e5ce2feef9ea1a49ac) Co-authored-by: itssme <itssme3000@gmail.com> | ||||
| * | #15545: fix sqlite3.iterdump regression on unsortable row_factory objects. | R David Murray | 2013-01-10 | 1 | -1/+2 |
| | | | | | | | | | | 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. | ||||
| * | Fix sqlite3.Connection.iterdump on tables/fields with reserved names or quotes | Petri Lehtinen | 2012-02-12 | 1 | -22/+28 |
| | | | | | Closes #9750 | ||||
| * | Added missing files for new iterdump method. | Gerhard Häring | 2008-03-29 | 1 | -0/+63 |
