U++ forum: Welcome to the forum

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

Wed, 14 July 2010 01:39

rylek
Messages: 79
Registered: November 2005

Member

Hi Tojocky!

Thanks, that was just a silly typo, of course the cases should match (WSTRING_V with WString and STRING_V with String). 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

Report message to a moderator