dear Ann,

>
> You've got
> some choices. You can pick one of the almost OK character sets. You
> can use UTF8 and not overspecify field lengths and choose field
> lengths that are likely to compress well with Firebird's RLE when
> they're empty. Or, you can use the fairly well defined interfaces for
> character sets and collations and define your own - or hire someone to
> do it for you.
>

yes off course, but i was also curious how many people was aware that their
UTF8 database can be much more slower than equivalent ASCII database :)
i m sure most of them don't know about it when they choose UTF8 ...





[Non-text portions of this message have been removed]