Am 01.02.2010 um 00:02 schrieb a1rex: > I am planning to store text in a database which has to accommodate a > few international languages. > In this case I have to use UTF-16LE encoding for my TEXT fields. > I know that once an encoding has been set for a database, it cannot > be changed.
Just another thought to consider: depending on the amount of non-ASCII (or non-roman) string data stored in your database, in may be more efficient to use UTF-8 encoding rather than UTF-16 encoding: UTF-8 takes up less space for ASCII or roman text, whereas it may take up more space for other characters. This really depends on the mix. However, we found that our database performance improved quite a bit when we switched back to UTF-8 (granted, most of the characters in our data can be represented by single-byte UTF-8 sequences), mainly due to the reduced overall database size (probably fitting more columns on a single page in the database, thus requiring less read operations to access a single record). But as I said, this depends a lot on the data you will store, the total size of the database and the structure of your tables, so you'll have to evaluate yourself... </jum> _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
