Jim Starkey wrote:

>>Jim, don't forget the field's default collation, before the session's.
>>
> I didn't forget it -- I left it out on purpose. In my mind, collation
> is a property of data manipulation operation, not the data itself. It
> may be useful as a default for indexes containing that field, but I
> don't think it should override the default collation specified by a
> client. I'm willing to concede that a declaration of case insensitivity
> expressed as a collating sequence doesn't work well with this model.
> I'm not happy with that, and I'm going to have to think about it some more.

The one thing that people seem to forget about is that the DATA does not
have any order at all, so as long as an index is available with a simple
primary key then any record can be found. It's only when you want to
order the data that you need the collation. And then you are creating an
'index' which can be a persistent item, or generated on the fly, but the
raw data will not be affected by that, so sorting case insensitive is no
different to any other sort?

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services