[Mono-list] Problem with Oracle and Mono Charset...
Mon, 28 Feb 2005 07:55:44 -0500
Sure, you can implement. We accept patches.
You could look at System.Data.SqlClient on how it does connection pooling.
Another way is to use some OCI functions for connection pooling. So,
you might have to create DllImport functions for these OCI functions.
Oracle 9i Call Interface Programmer's Guide
Hubert FONGARNAND wrote:
>Thank you for your fix... It works now without any problems...
>Just a question, do you plan to implement connection pooling on oracle client
>classes. I've seen that dealing with oracle database works well with mono
>(now) but it's much more slower than MS.NET when you open and close many
>connections... Is there a way to speed up this process.
>I'm ready to help you implementing this, if you need...
>Le Samedi 26 Février 2005 05:38, vous avez écrit :
>>I recently committed a fix to svn trunk HEAD for strings in
>>OracleParameter to use OCIUnicodeToCharSet for Oracle data types dates,
>>CLOBs, VARCHAR2/CHAR, etc...
>>Can you try your tests again to see if they work now? I do not know
>>French to test the changes. :-)
>>Hubert FONGARNAND wrote:
>>>Thanks to Daniel Morgan
>>>DataTime and OracleDateTime works now perfectly. There's still a problem
>>>with charset.When my NLS_LANG variable isn't set (on my mono client),
>>>french "éè" are seen as "??" in the database (MS.NET client see "??").
>>>The only way to display the "éè" correctly is to set my NLS_LANG to :
>>>NLS_LANG="FRENCH_FRANCE.UTF8" (but normally, the client should adapt
>>>itself to the server settings)
>>>but there's still a problem with string length. eg: when I do an "INSERT"
>>>with a string with some "éè" the string is "cut" by oracle, so I can not
>>>see the entire string in the database...