U++ forum: Welcome to the forum

Re: Oracle8: UTF8 charset Patch [message #27354 is a reply to message #27353]

Wed, 14 July 2010 08:56

tojocky
Messages: 607
Registered: April 2008
Location: UK

Contributor

rylek wrote on Wed, 14 July 2010 02:39

As concerns database character set: if I remember the documentation right, you normally don't need to know the database character set at all; it's considered a part of the internal communication protocol between the client and the server. The client receives the data from the server (in some encoding) and converts it to a "default" client-side encoding set up during client installation (when it's not initialized with OCIEnvNlsCreate).

I agree that using the UTF8 encoding is more general as it's independent of the client installation settings and can store Unicode characters, I just believe that in practice a specific territory-dependent character set is quite sufficient when you know the database / client encoding in advance.

As concerns DisableUtf8Mode(), I see it as an ugly hack for special cases and as one which ipso facto requires a programmer knowing it must be used before Login. It might ASSERT that the session is not open, all right.

Regards

Tomas

Tomas,

I used this patch for load oci.dll/so without install oracle client. Just provide the library with application.

About DisableUtf8Mode(), I thing is not ASSERT that the session is not open. It is not a system error and not need force to close the application.

Best Regard, Ion

Report message to a moderator