-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/12/2015 05:15 AM, Cal Leeming wrote: > I've been having a problem where iterdump() is exporting in a > format which is unsuitable for MySQL,
iterdump is part of pysqlite, and has no code from the official SQLite project. iterdump itself is just an inadequate 50 lines of python code: https://github.com/ghaering/pysqlite/blob/master/lib/dump.py BTW there is a python sqlite group which will suit your python <-> sqlite needs better: https://groups.google.com/forum/#!forum/python-sqlite > It seems the backup features of sqlite3 are not exposed in higher > level APIs such as Python, SQLite exposes a C API. It is then up to the wrappers to expose that in their wrapped form. pysqlite does expose it but seems to leave it out of the documentation. https://github.com/ghaering/pysqlite/blob/master/src/backup.c > and getting data out of a sqlite3 in-memory DB in python into a > file is proving to be a difficult task, something which is arguable > a common requirement. It is pretty simple. You can use the backup API, you can use textual dumps, and you attach databases and copy that way. I suggest posting to the python sqlite list with what it is you are trying to do. Disclosure: I'm the author of an alternate Python SQLite wrapper: http://rogerbinns.github.io/apsw/ Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlTc3AQACgkQmOOfHg372QSejACg5etNEUcBnNq0rKQV2cABkPo6 bjwAn0FagmG7B8jUxTCSEWDzLbMhOXwo =4h4h -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
