Apparently they didn't think through somet hings for Oracle. I use prpared statements for dynamic sql, so depending on the database I need to find out what the parameter token is. For Sql server it is '@', for Oracle it is ':'. There is a ParameterToken property from the Database object but it is protected so I can't plug the parameter token into the sql dynamically.
What I am getting at is that they provided support for Oracle but obviously no one tested using Prepared Statements with Oracle. They left an entire concept out of the unit tests which I am sure someone would have caught had they mapped out the feature set properly.
To be fair to the Ent lib team I did put up a thread on this and Scott replied back that indeed there was no way get the ParameterToken property. It is unclear to me how to use prepared statements with the enterprise library so it is possible that I am missing something here. All in all I do think they did a nice job on the library. I just want to make it clear to Scott and the rest of the team that I wasn't trying to slam them in any way.