Subject | Re: [firebird-support] Re: Collation or character set with parameter |
---|---|
Author | Ivan Prenosil |
Post date | 2003-07-04T00:37:35Z |
From: "Aage Johansen" <aagjohan@...>
(Otherwise you do not have to specify it in ORDER BY and WHERE clauses).
Do you have any examples which characters cause problems ?
Ivan
> Actually, I think the original query used "<" (not "starting"), the exampleYou do not have specified the collation in field definition ?
> 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...
(Otherwise you do not have to specify it in ORDER BY and WHERE clauses).
Do you have any examples which characters cause problems ?
> Anyway, why is it that I can use "collate" with a constant or fieldname,Probably because standalone parameter is "typeless" ?
> but not with a parameter?
Ivan