-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jean-Christophe Deschamps wrote: > First decide or determine what is (or shall be) your database > encoding. Even if SQLite has no problem storing ANSI (or EBCDIC or > anything else) strings untouched,
This isn't particularly good advice. SQLite works solely in Unicode. When you supply text it *must* be in either UTF8 or UTF16 according to the API being used. Sometimes it will appear that you can get by using a different encoding but that is just luck and things that operate on text will fail. The actual encoding used by the database is pretty much irrelevant and other than the pragma you can't even tell what it is nor would you care. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrl1fQACgkQmOOfHg372QSC5ACfUDFnyFkDt7YE4d0BivC42eHt 6zYAnRwQ2Vnod9OEYM2flWdld+VC4L3L =gFQA -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
