| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
(cherry picked from commit 2a3926fa51b7264787d5988abf083d8c4328f4ad)
Reverted per Serhiy's request.
|
| |
|
|
|
| |
(GH-108657) (#108674)
(cherry picked from commit 400a1cebc743515e40157ed7af86e48d654290ce)
|
| |
|
|
|
|
|
| |
(#108340) (#108564)
(cherry picked from commit d0160c7c22c8dff0a61c49b5304244df6e36465e)
Co-authored-by: Aviv Palivoda <palaviv@gmail.com>
|
| |
|
|
|
|
|
|
| |
(GH-9621)
Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
(cherry picked from commit affa9f22cfd1e83a5fb413e5ce2feef9ea1a49ac)
Co-authored-by: itssme <itssme3000@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Closes #9750
|
| |
|