More on Enterprise Library (EntLib), ODP.NET and type mapping
September 4, 2008
The last time I wrote about this I was a bit too fast to get all the intricate details down. One of those details blew up in my face today.
The main reason for why it took me the better part of the afternoon to sort out had to do with some really confusing name-setting. Here is was confused me;
- the namespace System.Data.Oracle Microsoft has provided a implementation of a Oracle client provider. Keyword: Microsoft -this implementation doesn’t contain all the functionality in Oracle databases.
- cause of that Oracle has given us the Oracle.DataAccess.Client or ODP.NET for short. In this you’ll have all the things you’ll need.
Both of these inherits from the generic DbCommand (and uses the same name for almost everything) and can hence be converted into DbCommand but not into each other (of course - but this took me about 1,5...