-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kevin Ryde wrote: > Or no doubt by querying it out, "sqlite3 old.db 'pragma encoding'". > But that's something .dump could helpfully do itself, could it?
The SQLite shell can't read your mind :-) Adding something like this would require yet another command line flag, more code for when you do want the encoding preserved and when you don't, testing both paths etc. The dump currently provides exactly one thing. If you dump one database into another then queries against both databases will give back identical results. If you want to fine tune (cache sizes, page sizes, encoding etc) then it is trivial to prefix the dump as appropriate. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAks79aUACgkQmOOfHg372QTy5wCg0682yyw8JNOxlSIdbSnLrI6q IlcAn0aZFhPzr94VA/KOPgYitjeWOAWo =vsJR -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
