On Thu, 3 Jul 2003 18:32:00 +0000 (UTC), Ivan Prenosil wrote:

>> SELECT ...
>> FROM ...
>> WHERE FIELDNAME STARTING 'Something' COLLATE NO_NO
>> ORDER BY FIELDNAME
>>
>> works OK, whereas
>
>
> Works OK? Are you saying that you see any difference between
> WHERE FIELDNAME STARTING 'Something' COLLATE NO_NO
> and
> WHERE FIELDNAME STARTING 'Something'
> (especially if Something contains national characters) ??
>
> afaik LIKE and STARTING operators does not care about collation at all.

Actually, I think the original query used "<" (not "starting"), the example
with "starting" was just used when we experimented in ib_sql.
We tried different ways with character set (_iso8859_1) and collating
sequence (no_no), but we were always unsuccessful (with the
lookupcombo). Trying to use _iso8859_1/no_no with the parameter was a last
desperate effort.
If we don't use collate in the order by, some (Swedish, in this case)
letters create problems in the ordering, causing the functionality of the
lookupcombo to fail. If we _do_ use the collate, it just fails in another way!
Maybe the time has come to create our own collation...

Anyway, why is it that I can use "collate" with a constant or fieldname,
but not with a parameter?


--
Aage J.