> About the endieness, you don't need to know if you > don't care. SQLite handles it.
SQLite does handle that, but what would be the performance loss when working with a UTF-16 encoded database, but with endianness opposite to the system? That's quite probable scenario, say, a database created on Intel-based system and then moved to Mac/PPC. Best regards, Igor -----Original Message----- From: Nuno Lucas [mailto:[EMAIL PROTECTED] Sent: Friday, November 23, 2007 2:01 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] benchmarking UTF8 vs UTF16 encoded databases On 11/23/07, Jarl Friis <[EMAIL PROTECTED]> wrote: > Hi Daniel. > > Thanks for the benchmark reports, interesting studies. > > Another reason to stay away from utf-16 is that it is not endianess > neutral. Which raise the question are you storing in UTF-16BE or > UTF-16LE ? If you only speak Japanese and all your characters are 3 bytes or more in UTF-8 and always 2 bytes in UTF-16 which would you tend to choose? About the endieness, you don't need to know if you don't care. SQLite handles it. Regards, ~Nuno Lucas > > Jarl ---------------------------------------------------------------------------- - To unsubscribe, send email to [EMAIL PROTECTED] ---------------------------------------------------------------------------- - ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
