blocks|key|410590|text|我认为您可以创建自己的提供程序，使用您想要使用的默认值。您可以通过继承odp.net的所有类来轻松创建该提供程序，只需调整一些属性，如BindByName。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|410591|DbProviderfactory将创建您的类，而不是普通的odp.net类。|410592|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I think you can create your own provider that uses the defaults you want to use. You could create that provider easily by inheriting all the classes from odp.net, just adjust some properties like BindByName. 

The DbProviderfactory will create your classes instead of the normal odp.net classes.

blocks|key|3254576|text|至于停止使用Microsoft+ADO+.NET+provider+for+Oracle：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3254577|我将继续使用它而不是|3254578|+.NET，你的问题只是它众多问题中的一个。随着它的发展，它在ADO4.0中仍然可用，尽管unsupported.|unordered-list-item|3254579|If+.NET设法使这个提供程序不可用，但我可能会使用完全集成到ADO+.NET框架中的商业替代方案，如DataDirect+ADO.NET+Data+Provider+for+Oracle或dotConnect+for+Oracle。顺便说一句，他们已经支持实体框架了(我相信甲骨文声明的ODP.NET不会)。|offset|length|3254580|3254581|ODP+.NET已经占用了我太多的时间。|3254582|entityMap|0|LINK|mutability|MUTABLE|url|http://www.datadirect.com/products/net/net_for_oracle/index.ssp|1|http://www.devart.com/dotconnect/oracle/^0|0|0|0|1G|17|0|2O|L|1|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|10|8|@]|9|@$I|11|J|12|1|13]|$I|14|J|15|1|16]]|A|$]]|$1|K|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]]]

As for the discontinuation of the Microsoft ADO .NET provider for Oracle :

<ul>
<li>I will go on using it instead of ODP .NET, your problem being only one of the numerous issues with it. And as it goes, it will still be available in .NET 4.0, though unsupported.</li>
<li>If Oracle manages to render this provider unusable, I will probably go with a commercial alternative such as <a href="http://www.datadirect.com/products/net/net_for_oracle/index.ssp" rel="nofollow noreferrer">DataDirect ADO.NET Data Provider for Oracle</a> or <a href="http://www.devart.com/dotconnect/oracle/" rel="nofollow noreferrer">dotConnect for Oracle</a>, that fully integrate into the ADO .NET framework. And they already support the Entity Framework, by the way (I believe Oracle stated ODP .NET would not).</li>
</ul>

ODP .NET took too much of my time already.

blocks|key|413697|text|使用间接和继承！如果通过抽象数据库类执行数据访问，则需要Database实现句柄参数绑定。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|413698|public+abstract+class+Database
{
++++private+readonly+DbProviderFactory+factory;

++++protected+Database(DbProviderFactory+factory)
++++{
++++++++this.factory+=+factory;
++++}

++++public+virtual+DbCommand+CreateCommand(String+commandText)
++++{
++++++++return+CreateCommand(CommandType.Text,+commandText);
++++}

++++public+virtual+DbCommand+CreateCommand(CommandType+commandType,+String+commandText)
++++{
++++++++DbCommand+command+=+factory.CreateCommand();
++++++++command.CommandType+=+commandType;
++++++++command.Text+=+commandText;
++++++++return+command;
++++}

++++public+virtual+void+BindParametersByName(DbCommand+command)
++++{

++++}
}|code-block|syntax|javascript|413699|并选择创建覆盖默认命令创建的Oracle特定实现，或提供按名称绑定参数的选项。|413700|public+class+OracleDatabase+:+Database
{
++++public+OracleDatabase()
++++++++:+base(OracleClientFactory.Instance)
++++{

++++}

++++public+override+DbCommand+CreateCommand(CommandType+commandType,+String+commandText)
++++{
++++++++DbCommand+command+=+base.CreateCommand(commandType,+commandText);
++++++++BindParametersByName(command);
++++++++return+command;
++++}

++++public+override+void+BindParametersByName(DbCommand+command)
++++{
++++++++((OracleCommand)command).BindByName+=+true;
++++}
}|413701|基于中的的代码。|413702|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Use indirection and inheritance! If you're performing data access through an abstract Database class, require the Database implementation handle parameter binding.

<pre><code>public abstract class Database
{
 private readonly DbProviderFactory factory;

 protected Database(DbProviderFactory factory)
 {
 this.factory = factory;
 }

 public virtual DbCommand CreateCommand(String commandText)
 {
 return CreateCommand(CommandType.Text, commandText);
 }

 public virtual DbCommand CreateCommand(CommandType commandType, String commandText)
 {
 DbCommand command = factory.CreateCommand();
 command.CommandType = commandType;
 command.Text = commandText;
 return command;
 }

 public virtual void BindParametersByName(DbCommand command)
 {

 }
}
</code></pre>

And choose to create an Oracle specific implementation that overrides default command creation or provides the option to bind parameters by name.

<pre><code>public class OracleDatabase : Database
{
 public OracleDatabase()
 : base(OracleClientFactory.Instance)
 {

 }

 public override DbCommand CreateCommand(CommandType commandType, String commandText)
 {
 DbCommand command = base.CreateCommand(commandType, commandText);
 BindParametersByName(command);
 return command;
 }

 public override void BindParametersByName(DbCommand command)
 {
 ((OracleCommand)command).BindByName = true;
 }
}
</code></pre>

Code based on the <a href="http://msdn.microsoft.com/en-us/library/dd203144.aspx" rel="nofollow noreferrer">Data Access Application Block</a> in the <a href="http://msdn.microsoft.com/en-us/library/cc467894.aspx" rel="nofollow noreferrer">Enterprise Library</a>.

I'm currently using the Microsoft ADO.NET provider for Oracle (<code>System.Data.OracleClient</code>). I'm aware that it is certainly not the best Oracle provider available and that it <a href="http://blogs.msdn.com/adonet/archive/2009/06/15/system-data-oracleclient-update.aspx" rel="noreferrer">will soon be deprecated</a>, I should be using Oracle's ODP.NET instead. The reason why I still use the MS provider is because ODP.NET binds parameters by position, not by name. This can really be a PITA when you use many parameters in a query, because you have to be careful to add them in the right order, which can easily lead to bugs. It's also annoying when you use the same parameter multiple times in the same query, for instance :

<pre><code>SELECT A,B,C FROM FOO WHERE X = :PARAM_X OR :PARAM_X = 0
</code></pre>

With ODP.NET, I have to add two parameters to the <code>OracleCommand</code>, which I think is stupid...

ODP.NET's <code>OracleCommand</code> has a property to change that default behavior : <code>BindByName</code>. When set to true, the parameters are bound by name, which is what I want. Unfortunately this doesn't really help me, because :

<ul>
<li>It is set to false by default</li>
<li>I almost never use concrete ADO.NET classes explicitly, I prefer to use ADO.NET 2.0 abstraction layer (<code>DbProviderFactory</code>, <code>DbConnection</code>, <code>DbCommand</code>...) to reduce coupling to any specific RDBMS. So I don't have access to the <code>BindByName</code> property, unless I cast explicitly to <code>OracleCommand</code>, losing all the benefits or the abstraction.</li>
<li>When using an ASP.NET SqlDataSource, I don't create the DbCommand myself, so I don't get a chance to set <code>BindByName</code> to true (I could do it in the Selecting event, but it really is a pain to do it for each SqlDataSource...)</li>
</ul>

How am I supposed to handle that issue ? Is there a <code>BindByNameByDefault</code> setting somewhere ? (I didn't find anything like that, but I may have missed it...)

Binding query parameters by name with ODP.NET

数据库

我目前使用的是Microsoft (System.Data.OracleClient)。我知道它肯定不是最好的甲骨文提供商，而且它是的，我应该改用甲骨文的ODP.NET。我仍然使用MS提供程序的原因是因为ODP.NET通过位置而不是名称来绑定参数。当您在查询中使用许多参数时，这可能真的是一个难题，因为您必须小心地以正确...

问使用ODP.NET按名称绑定查询参数
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用ODP.NET按名称绑定查询参数EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用ODP.NET按名称绑定查询参数
EN