[issue34828] sqlite.iterdump does not work for (most) databases with autoincrement

Change by Erlend E. Aasland : -- nosy: +erlendaasland ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue34828] sqlite.iterdump does not work for (most) databases with autoincrement

Joel Klimont added the comment: I made the pull request: https://github.com/python/cpython/pull/9621 -- ___ Python tracker ___ ___

[issue34828] sqlite.iterdump does not work for (most) databases with autoincrement

Change by Joel Klimont : -- keywords: +patch pull_requests: +9019 stage: needs patch -> patch review ___ Python tracker ___ ___ Pyth

[issue34828] sqlite.iterdump does not work for (most) databases with autoincrement

Berker Peksag added the comment: > I have already forked the repository, written tests etc. and if you > want I will create a pull request. Please do! Note that 3.4 and 3.5 are in security-fix-only mode and let's decide whether fixing 2.7 is worth the trouble when you submit your PR. Thank y

[issue34828] sqlite.iterdump does not work for (most) databases with autoincrement

New submission from Joel Klimont : There is a bug in sqlite3/dump.py when wanting to dump databases that use autoincrement in one or more tables. The problem is that the iterdump command assumes that the table "sqlite_sequence" is present in the new database in which the old one is dumped in