U++ forum: Welcome to the forum

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

Tue, 13 July 2010 08:36

tojocky
Messages: 607
Registered: April 2008
Location: UK

Contributor

rylek wrote on Tue, 13 July 2010 02:20

Hi there!

After playing with one of my applications which started to malfunction after Mirek applied tojocky's patch I found out that the patch doesn't solve all related problems and in fact creates new ones.

Hello Tomas,

Thank you for testing my patch and improve the functionality.

Quote:

have the default application charset set to WIN1250. The databases on the servers have the same codepage so no conversion is necessary.

When you load the library and try to connect to the database you do not know the DB encoding! The solution I found to set utf8 charset.

Your patch is very useful. My default charset of application is UTF8 and I did not need to convert the data to/from utf8. Thanks!

But I can't understand:

void  OCI8Connection::SetParam(int i, const Value& q) {
.................
case STRING_V:
				SetParam(i, WString(q));
				break;
			case WSTRING_V:
				SetParam(i, String(q));
				break;
...................
}

You convert into string if type is WString and vice-versa. Why?

Quote:

DisableUtf8Mode turns off the new OCIEnvNlsCreate-related code and leaves the client communicating in the native character set

How to prevent the user if he tries to DisableUtf8Mode after connected. Nothing happening?

The problems with Oracle 8 is: the charset OCI_NLS_NCHARSET_ID_UT8 is not true UTF8 and may create some problems. I test my patch with Oracle 10 (uses OCI_NLS_NCHARSET_ID_AL32UT8) and works fine with my default charset of application UTF8!

Thanks for patch.

Report message to a moderator