tnx for the quick replay.
> when using collate NOCASE on some column definition, how does a
> specific element is chose to be returned, the upper case, the lower
> case or the first one appears?
>Collation doesn't affect how the data is stored, just how it's compared.
>You will get your strings out in exactly the same form you put them in.
lets say i have the following table:
create table t1 (col1 text collate nocase)
insert t1 values {a}
insert t1 values {A}
and then i execute the following:
select col1
from t1
group by col1
the result will be: a or A?
On 11/7/07, Igor Tandetnik <[EMAIL PROTECTED]> wrote:
>
> Aviad Harell <[EMAIL PROTECTED]>
> wrote:
> > is there any implications on performance of using collate i(NOCASE for
> > example) in the column definition when creating a table? doesn't it
> > effect the indexes use of those columns?
>
> If you also create an index on this column, and don't explicitly specify
> what collation the index should use, it would use the collation declared
> on the column. If no collation is specified anywhere, the default is
> COLLATE BINARY.
>
> > when using collate NOCASE on some column definition, how does a
> > specific element is chose to be returned, the upper case, the lower
> > case or the first one appears?
>
> Collation doesn't affect how the data is stored, just how it's compared.
> You will get your strings out in exactly the same form you put them in.
>
> Igor Tandetnik
>
>
>
> -----------------------------------------------------------------------------
> To unsubscribe, send email to [EMAIL PROTECTED]
>
> -----------------------------------------------------------------------------
>
>
