Re: OracleType.NVarChar parameters handled differently in framework 1.1?
From: SqlJunkies User (User_at_-NOSPAM-SqlJunkies.com)
Date: 05/18/04
- Next message: Christian Boult: "Re: Exception in DataTable.Select"
- Previous message: William Ryan eMVP: "Re: RowFilter with *"
- In reply to: SmokeMe: "OracleType.NVarChar parameters handled differently in framework 1.1?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 May 2004 09:30:05 -0700
Set your IDbDataParameter.DbType to DbType.AnsiString and everything should work as before.
When using an OracleParameter instance of the IDbDataParameter interface, it appears as though setting the parameter.DbType to DbType.String or DbType.StringFixedLength causes the Oracle instance OracleParameter.OracleType to change to OracleType.NVarChar or OracleType.NChar respectively. If you set the DbType to DbType.AnsiString or DbType.AnsiStringFixedLength, however, the OracleParameter.OracleType seems to map to the OracleType.VarChar and Char respectively. I discovered this with some trial and error. A simple Search and replace of all your DbType.String to DbType.AnsiString should do the trick for you and not break any of your existing SQL and OleDB use of IDbDataParameter. Let me know if this works for you or if you find another solution.
--- Posted using Wimdows.net NntpNews Component - Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
- Next message: Christian Boult: "Re: Exception in DataTable.Select"
- Previous message: William Ryan eMVP: "Re: RowFilter with *"
- In reply to: SmokeMe: "OracleType.NVarChar parameters handled differently in framework 1.1?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|