Subject Re: Character set was RE: Digest Number 1619
Author p_lerner
Well, I'm sorry to be remembering you to Forest Gump, but my problem
now is
my apparently lack of experience with SQL. I have decided to try ISO
ES_ES, to see how it works, and have been triyng to do what Helen

"UPDATE ordcompra
set newFld = ISO8859_1 oldFld
where oldFld is not null"

newFld: varchar(70) CHARSET: ISO8859-1 COLLATION: ES_ES

The problem is that I get :
"Invalid token.
Dynamic SQL Error.
SQL error code = -104.
Token unknown - line 2, char 24.

I also have try:
"update ordcompra
set prueba = cast(orc_motivo as VARCHAR(70) CHARACTER SET ISO8859_1)
where orc_motivo is not null"

but I get:
"Arithmetic overflow or division by zero has occurred.
arithmetic exception, numeric overflow, or string truncation.
Cannot transliterate character between character sets."

What am I missing ? I've been reading some languaje reference and SQL
reference docs but didn't find how to make it work. No doc indicates
how to
cast a char set field.

--- In, "peter_jacobi.rm"
<peter_jacobi@g...> wrote:
> The ISO 8859-1 character set and its <language>_<country>
> collations are technically best. You should try the resulting
> sort order of ES_ES with your data and decide whether you agree.
> Punctuation characters are ignored by the <language>_<country>
> sort order which is both standard conforming and useful, but
> surprises some people. Check for yourself.
> More information than you may ever want to know at:
> All UNICODE characters in PDF charts:
> Interactive character reference:
> start here if you don't know where to start:
> Crossreferences of other character sets to UNICODE
> Regards,
> Peter Jacobi
> Hamburg, Germany