[Mono-list] Mono and Oracle OCI character set encoding
james.dalton at deltadentalva.com
Wed Sep 9 17:09:11 EDT 2009
I'm not really forking System.Data.OracleClient. While there are missing
features, there is also a lot that we don't need so I'm starting from
scratch and implementing only what we need in a way that fits our
application best. If I manage to get this working and going with mono
doesn't get shot down and the bosses approve, I wouldn't have a problem
contributing to either System.Data.OracleClient or a fork or both. Right now
that's a lot of ifs though.
I've got OCI session pooling working, getting data from a ref cursor is no
problem (even strings.) I'm sure I'm missing something simple or something
that Mono is doing behind my back when getting a string from OCI verses
sending one to OCI.
Now that I think about it, maybe what I need to do is pull the source for
mono and see what is happening when the call is made. (My head is still
stuck in proprietary land.)
I was considering forking System.Data.OracleClient myself to get missing
features that are found in ODP.NET, but I haven't.
Are you keeping this fork in some public source code repository? This would
allow others to contribute patches.
View this message in context: http://www.nabble.com/Mono-and-Oracle-OCI-character-set-encoding-tp25368213p25373172.html
Sent from the Mono - General mailing list archive at Nabble.com.
More information about the Mono-list