Re: RFC: (NT-related) optimization

--- In sqlite-F5Bj5G+ccuY@xxxxxxxxxxxxxxxx, "sword@xxxx" <sword@xxxx> wrote:
> Hi everyone,
> 
> I'm new to SQLite and evaluating it to use it in a program that will
> run on MS Windows 2000/XP, without compatibility to Win9X ...
> I would like to know how the design decisions will be done to the
> following points in SQLite before re-inventing wheels.

> 3. UTF-16
> 
> ... UTF-8 is proposed, but how about UTF-16(little-endian UCS-2)?
> It is the internal code of NT platforms and Windows has a set of APIs
> to handle those wide characters. Surely database size will be larger if
> UTF-16 is used, but interaction will be the most natural in Windows.
> Without UTF-16 support, storing UTF-16 strings always involves
> binary encoding.

UTF8 is already supported. What has been talked about recently is
dynamically deciding whether/not the sqlite library should treat text
as ASCII or UTF8.

Sqlite currently stores data internally as 0-terminated byte strings.
It is considered a major architectural change to directly store binary
data containing 0s.

Since only a very few API functions are usually needed with sqlite,
you may want to just create wrapper functions for them using
sqlite_encode/decode_binary(). The translation overhead may not be as
bad as you think, especially if you're using European text, in which
case the UTF8 encoding may end up compressing the text. Sqlite is an
I/O bound process (unless you memmap the file).

Jim Lyon




------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/CBxunD/vN2EAA/xGHJAA/EbFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
sqlite-unsubscribe-VgYJa0VH1e9BDgjK7y7TUQ@xxxxxxxxxxxxxxxx

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/