Subject | Re: [Firebird-Architect] UTF-8 over UTF-16 WAS: Applications of Encoded Data Streams |
---|---|
Author | Jim Starkey |
Post date | 2005-05-04T03:38:33Z |
Adriano dos Santos Fernandes wrote:
default collation. But that doesn't necessarily have anything to do
with the way the database stores things internally. People give numbers
in ascii decimal; surely you don't object to storing them in binary?
I think our goal should be to simplify and speed up the database
engine. If there isn't a pressing to need to maintain multiple
character sets within the engine, it's something we can and should forgo
in favor of simplicity.
>Jim Starkey wrote:I have no problem setting the character set of fields to indicate a
>
>
>
>>You may have a point; there are many more Chinese than Europeans, so a
>>global optimization suggests that a bias towards larger character sets
>>is warranted.
>>
>>
>Why choose one side if all can be satisfied?
>Some people are inteligent enough to set the character set of your
>fields. ;-)
>
>
>
>
default collation. But that doesn't necessarily have anything to do
with the way the database stores things internally. People give numbers
in ascii decimal; surely you don't object to storing them in binary?
I think our goal should be to simplify and speed up the database
engine. If there isn't a pressing to need to maintain multiple
character sets within the engine, it's something we can and should forgo
in favor of simplicity.