Re: Whatcha' wanta have?????

How could i forget this one? case insensitive comparisons and collating order! I don't want that applied to CHAR and VARCHAR types, since they are fast'n'mean byte-wise datatypes. However, since NCHAR and NVARCHAR fields can have a GLS locales applied, they are ideal for this little extension. I cannot find an English Locale that has case-insensitive collation. I don't know about other european GLS locales, but I'd wager they are case sensitive too, but could profit from caseless. I'm not sure that everyone would WANT all strings to be caseless; for us we would want codes to be sensitive but many description strings to be insensitive, but we could get away with using CHAR and NCHAR as appropriate. People using French, German, et. al. would not have that luxury. Therefore i think that GLS locales need to be provided with an inbuilt alternative to the case sensitivity of the collation, and then NCHAR and NVARCHAR fields could have an optional WITH NO CASE (c.f. NOT NULL) to set the field to one style or the other. Once again, to repeat, plain ole' CHAR fields should not be affected in any way.