On Wed, Nov 03, 2004 at 03:00:01PM +0100, Martin Stjernholm, Roxen IS @ Pike developers forum wrote:
perhaps add a flag somewhere to explicitly turn it off (but I suggest that you make some actual measurements of what you'll gain with it
The gain is: 1) Less memory - I don't need temporary buffers for conversion. Every new string creation is a pain - when you have a lot of them... 2) Less CPU usage - on short sequecnes this is almost invisible, but when you have gigabytes of data - it makes visible load.
Well, come to think of it, a third option is actually to do it conditionally and also store a flag which tells whether it was UTF8 encoded or not.
Unfortunately, there is no place for such flag in database - sqlite doesn't support any tagging (only 4 basic types, 2 of them integers, 1 binary and 1 text). I would prefer a flag (in connection/object) like "pass data as is" or (preferably) "make conversion" (so it won't be default, since this is not done anywhere else by default), i.e. without any implicit conversions, and handle results on my own.
In any case, when it's time to decode the string you have to _know_ if it's to be UTF8 decoded or not.
Sure, but better if I can control when (and where) it is done.
If flag (method) is OK, then it is OK for me (I wonder, is there someone who actually uses (or plans to) SQLite?) :)
Regards, /Al