Hi Svein,

Casting the special character is the solution.

select tipo || cast('/' char(2)) || direccion from direccion

character set is not necesary in this situation.

Thanks a lot.
Danny

Svein Erling Tysvaer escribió:

>
> Have you tried workarounds like e.g.
>
> select tipo || cast('/ ' as char(2) character set NONE)|| direccion
> from direccion
>
> or
>
> select tipo || cast('/ ' as char(2) character set ISO8859_1 collation
> ES_ES) || direccion
> from direccion
>
> (or whatever the Spanish collation is called)
>
> I'm just guessing a possible workaround, I've never used character set
> NONE - all my databases tend to be character set ISO8859_1 collation
> NO_NO and I've never had problems concatenating strings (or maybe I've
> concatenated strings that became too long, but if so, I've forgotten
> that).
>
> HTH,
> Set
>
> Danny Garcia Hernandez wrote:
> > Hi Adriano, i using FB 1.5.1, in this revision this problem is fixed.
> >
> > Remember that i can select from columns data in ISO8859_1 charset. The
> > problem is when i try to concatenate this data using || operator and
> > special characters. In a adreess table i have separated field that
> > conform (all) the complete address. Right now, i have a process that
> > conform the complete address folowing some rulesand insert it Av/
> > Liberty # 100) into one column in other table.
> >
> > select tipo || direccion || numero || piso || puerta from direccion
> [ OK.]
> >
> >
> > select tipo || '/ ' || direccion || ' ' || numero || ' ' || piso || ' '
> > || puerta from direccion [ FAIL (direccion field contain a Ó
> character).]
> >
> > Thanks
> > Danny
> >
> > Adriano dos Santos Fernandes escribió:
> >> Danny Garcia Hernandez escreveu:
> >>> Sorry, i'm getting this error message.
> >>>
> >>> ERROR: Cannot transliterate character between character sets.
> >>>
> >> What version are you using?
> >>
> >> AFAIR, such type of problem was fixed in one of the 1.5 point releases,
> >> with the patch changing NONE charset behavior.
> >>
> >> Adriano
>
>