Re: NLS question
Date: Wed, 16 Mar 2011 08:45:45 +0200
Message-id: <4D805C99.4040909_at_inter.net.il>
I beg to differ.
If you try to insert a character that is illegal in the client charset,
to a database that has a different charset, it will put ascii 61 or 191
in the database.
So you can not know what the client tried to write, like the problem
that started this thread.
Since the client does the translation the database gets garbage and
there is no way to retrieve the original data that was intended to store
in the database.
The only way to get exactly what is in the database is to use a client with charset that is EXACTLY the same charset as the DATABASE. This way there is no conversion and you get the data from the database, even if it contain characters that are illegal in the charset you use.
Yechiel Adar
Israel
On 15/03/2011 02:28, De DBA wrote:
> The solution is to set the NLS_LANG parameter in the environment of
> the querying client to whatever it defaulted to on the inserting client,
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Mar 16 2011 - 01:45:45 CDT