Subject | Re: [ib-support] Re: Case Sensitivity on Indices |
---|---|
Author | Martijn Tonies |
Post date | 2003-01-16T11:14:16Z |
Hi,
Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
> > Just had a try with ISO8859_1, collation DU_NL -No difference.
> > when I ORDER a column with these values:
> >
> > And
> > AND
> > aNd
> >
> > it ens up like:
> >
> > aNd
> > And
> > AND
> >
> >
> > While using collation ISO8859_1 (the default), I get:
> >
> > AND
> > And
> > aNd
> >
> > So there does seem to be a difference there...
>
> that's strange; I (almost clearly <g>) remember that (at least with
> collation IT_IT which I once tried) the results were different; but
> perhaps I'm confusing case sensitivity and accent sensitivity here.
>
> > btw - when using the columns in a WHERE clause, they
> > make no difference and never return "all" rows when doing
> > = 'AND'
>
> did you try
>
> select ... from ...
> where somefield collate DU_NL = 'AND' collate DU_NL
>
> ?
> Or perhaps you have defined the collation at the column level and triedIt is defined at column level.
> select ... from ...With regards,
> where somefield = 'AND' collate DU_NL
>
> ?
>
> Since the comparisons must obey to the same rules whether they are done
> for sorting and for filtering, if you experience different behaviour
> there must be a bug somewhere.
Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."