Subject | Re: [Firebird-Architect] Re: UTF-8 (various) |
---|---|
Author | Jim Starkey |
Post date | 2005-03-04T18:22:33Z |
Daniel Rail wrote:
insensitivity. I think we can also agree that a collation is required
to define case insensitivity for a particular language. The question is
whether case insensitivity is, in fact, just a collation, or something a
little stronger. The difference, I think, is in the definition of the
equality operator. For field declared as case insensitive, two values
can be different but still equal. Furthermore, a comparison of field
that is case insensitive to a case sensitive value must be performed
with case insensitivity. Should the same rules apply to simple
collations? It seems funny that a client can request a case insensitive
order of values but not a case insensitive retrieval by value.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376
>>Are there other collations where equality is collation specific?Good. Let's accept the idea that there are different flavors of case
>>
>>
>
>Accent insensitivity combined with case insensitivity equalities.
>
>
>
insensitivity. I think we can also agree that a collation is required
to define case insensitivity for a particular language. The question is
whether case insensitivity is, in fact, just a collation, or something a
little stronger. The difference, I think, is in the definition of the
equality operator. For field declared as case insensitive, two values
can be different but still equal. Furthermore, a comparison of field
that is case insensitive to a case sensitive value must be performed
with case insensitivity. Should the same rules apply to simple
collations? It seems funny that a client can request a case insensitive
order of values but not a case insensitive retrieval by value.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376