joergr at voelcker.com
Fri May 7 10:47:21 EDT 2004
> -----Original Message-----
> From: mono-devel-list-admin at lists.ximian.com
> [mailto:mono-devel-list-admin at lists.ximian.com] On Behalf Of
> Eduard Nesiba
> Sent: Friday, May 07, 2004 4:04 PM
> To: mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-devel-list] System.Data.OracleClient
> Hello Jörg,
> In OCI exists functions
> OCINlsGetInfo(dvoid *hndl, OCIError *errhp, OraText *buf,
> size_t buflen,
> ub2 item)
> with 'EvnHandle' and 'NLS_CHARACTER_SET'
> we can get client NLS charset
> OCINlsNameMap( dvoid *hndl, oratext *buf, size_t buflen,
> const oratext *srcbuf,
> word flag)
> With 'OCI_NLS_CS_ORA_TO_IANA' we can get client ISO charset name.
> Have you any idea where is better place to call this functions
> and set this attribute for current connection to be avialable
> in OciDefineHandle and OciStatementHandle?
These functions seem to be usefull for our problem.
I would create the Encoding only once in OciEnvironmentHandle
which could make it available as public property. OracleCommand
should then be able to hand it over to OciStatementHandle, etc.
> PS: Can you commit my patch to CVS without charset changes?
Unfortunately I have no CVS account yet. Could someone else
please check this part in?
More information about the Mono-devel-list