On Sun, 26 Oct 2003 12:39:40 -0500 "Mrs. Brisby" <[EMAIL PROTECTED]> wrote: > Further: I always read statements like "Microsoft C/C++ is the largest > most popular language platform in the world" as foolish sentiment. These > people obviously don't know what they're talking about and need a good > healthy dose of some reality. SQLite made the right decision to support > UTF-8. It did it largely for technical reasons but maybe in SQLite 3.0 > it'll be able to natively store binary blobs and MAYBE UCS-16 will be > possible and convenient at that point.
What is UCS-16? DO you mean UCS2? I, for one, like to see UCS2-enabled (or native-blob-enabled) SQLite just to ease my development on MS Windows. IIRC I've not heard anything about SQLite 3.0 and blob, or other future design, especially from D. Hipp himself. Please don't speak as it exists now. And what's so bad with someone who just wants to ease his burden? And for technical reason, it's the limit of current SQLite implementation and C language library, not today's general one. Null-terminated string can save space and time for relatively short strings, which are common in some simple address book database, but for better performance with long strings that probably SQLite is heavily conscios of, I still think it's odd design all data are null-terminated, though I have no solid benchmark. (Note that I don't talk about UCS2 here, because as it takes more space on disk performance degrades) As for Unicode, UTF-8 is good and very popular these days to be nearly standard, but it's clearly poor in character-wise computation performance compared to UTF-16, from programmer's point of view, or "technical reason". In UTF-8 you have 1-byte character or 3-byte character or 15-byte character, while in UTF-16 you have only 16bit characters or two 16bit character pairs. Not only VB has it as internal character representation, but also newer C# and .NET has, though it can export UTF-8 string. UTF-16 is also used in MacOS X and its HFS+ file system, as in MS Windows and NTFS. Since there are those filesystems with UTF-16 interface, I'd like to see UCS2/UTF-16 filename interface in SQLite while I don't want to store UCS2 natively as data at this time, please take a look at http://www.sqlite.org/cvstrac/tktview?tn=239 SQLite *does* provide MS Windows version anyway, why don't do as they do? -- KL --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
