Re: Western European database characterset
- From: "Yong Huang" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "yong321@xxxxxxxxx" for DMARC)
- To: "Markus.Zwettler@xxxxxxxxxx" <Markus.Zwettler@xxxxxxxxxx>
- Date: Fri, 7 Nov 2014 15:16:21 +0000 (UTC)
> My point has been that I might run into conversion errors using the
> combination
> client WE8MSWIN1252 / database WE8ISO8859P1[5].
> That’s why I would prefer the combination client WE8MSWIN1252 / database
> WE8MSWIN1252 for non-unicode applications.
Markus,
Your second option is obviously better. It's always a good idea to have client
and server both use the same character set. Your earlier message seems to imply
WE8MSWIN1252 is only for Windows. That's not true, even though the name has
"MSWIN" in there.
We've switched almost all our databases to using AL32UTF8, which is recommended
by Oracle. Only one vendor is stubborn. I hope they won't store the Euro symbol
in the database, or at least not store it and then retrieve it with a random
character set client.
Yong Huang
Other related posts:
