-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kevin Ryde wrote: > Perhaps it doesn't matter to anything.
The only effect is what happens behind the scenes. If you primarily use the - -16 interfaces to bind and retrieve text then the database also being utf16 means you avoid SQLite doing a conversion (assuming the byte orders also match). Some SQLite internals like query parsing are UTF8 only anyway (ie the prepare-16 functions convert to UTF8 and call the UTF8 variants). There may also be size differences in your database depending on the distribution of code points in your text data and the size of strings in proportion to other data and SQLite's metadata. You can dress your immediate issue by doing this: (echo 'pragma encoding="UTF-16";' ; sqlite3 old.db .dump ) | sqlite3 new.db Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAks6wFQACgkQmOOfHg372QSioQCbBjDWAb1mSDKW4G3yOD1Igdz0 n2EAn19xGp4/HwJfj2Mgwqt8Sh9gjfCL =v0qa -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users