[读书心得] 需要在.net中使用ADO2.x的情况
2005-05-12 16:24
627 查看
今天有空翻了下《Professional ADO.NET Programming》,里面讲到了一个需要在.net使用老ado情况,感兴趣,贴出来给大家看看。
文中提到了有两种情况:
第一种情况:ado中有更加灵活的锁机制和游标类型,当应用程序几乎不会出现多用户共同连接的情况出现,并且你需要查看用户对数据源的操作时,ado可能是个更好的选择。
第二种情况:你需要使用Record和Stream对象,例如当需要使用OLE DB Provider for Exchange 2000(ExOLEDB),或者是Internet Publishing(MSDAIPP)的时候,就不得不使用ado了,因为它们在ado.net暂时还不被支持。
附上原文:
Using ADO 2.x in .NET
Although we've stressed that you should use ADO.NET rather than ADO whenever possible, there are still a couple of scenarios where there's really no alternative but to use traditional ADO. We've mentioned these already, but it's worth reiterating them in one place:
1 If you absolutely have to use a connected recordset, and need to be able to update the data source. One reason for this might be the more flexible lock and cursor types available in ADO. If your application has a small enough number of users to permit simultaneous connections and you need to be able to see changes to the data source as they are made, then ADO may be a better choice.
2 If you need to use the ADO Record and Stream objects, for example if you're using the OLE DB provider for Exchange 2000 (ExOLEDB) or Internet Publishing (MSDAIPP). Until the OleDb provider is updated to support the OLE DB 2.5 interfaces or .NET providers for these data sources become available, you'll need to use ADO.
文中提到了有两种情况:
第一种情况:ado中有更加灵活的锁机制和游标类型,当应用程序几乎不会出现多用户共同连接的情况出现,并且你需要查看用户对数据源的操作时,ado可能是个更好的选择。
第二种情况:你需要使用Record和Stream对象,例如当需要使用OLE DB Provider for Exchange 2000(ExOLEDB),或者是Internet Publishing(MSDAIPP)的时候,就不得不使用ado了,因为它们在ado.net暂时还不被支持。
附上原文:
Using ADO 2.x in .NET
Although we've stressed that you should use ADO.NET rather than ADO whenever possible, there are still a couple of scenarios where there's really no alternative but to use traditional ADO. We've mentioned these already, but it's worth reiterating them in one place:
1 If you absolutely have to use a connected recordset, and need to be able to update the data source. One reason for this might be the more flexible lock and cursor types available in ADO. If your application has a small enough number of users to permit simultaneous connections and you need to be able to see changes to the data source as they are made, then ADO may be a better choice.
2 If you need to use the ADO Record and Stream objects, for example if you're using the OLE DB provider for Exchange 2000 (ExOLEDB) or Internet Publishing (MSDAIPP). Until the OleDb provider is updated to support the OLE DB 2.5 interfaces or .NET providers for these data sources become available, you'll need to use ADO.
相关文章推荐
- .net下导致Session失效的一种情况:js教本中使用window.open和window.showModalDialog时需要注意
- .net下导致Session失效的一种情况:js教本中使用window.open和window.showModalDialog时需要注意
- .net下导致Session失效的一种情况:js教本中使用window.open和window.showModalDialog时需要注意
- .net下导致Session失效的一种情况:js教本中使用window.open和window.showModalDialog时需要注意
- 什么是连接池:Ado.net连接池使用总结:什么情况下需要禁用连接池?
- ADO控件使用心得
- 利用SQLite ADO.NET在.NET(C#)中使用SQLite数据库
- .net 下对于List的使用心得总结
- SPRING事务的属性有哪些?其中,事务隔离级别有哪几种?什么情况需要使用这几种事务隔离级别?
- 不安全代码只会在使用/unsafe编译的情况下出现 .net问题
- struts2.X心得9--struts2自定义拦截器以及文件上传等几个拦截器使用案例
- 在ASP.NET AJAX中,由于一个ASPX页面上只能有一个ScriptManager控件,所以在有母版页的情况下,如果需要在Master-Page和Content-Page中需要引入不同的脚本时,这就需要在Content-page中使用ScriptMa
- .Net中偶尔需要使用异步的处理
- .NET : 监控ASP.NET应用程序的缓存使用内存数变化和命中情况
- .NET 使用ORACLE ADO.NET 经常会遇到的问题
- 哪些情况需要使用序列化?
- 用 .NET Memory Profiler 跟踪.Net应用内存使用情况
- 利用SQLite ADO.NET在.NET(C#)中使用SQLite数据库
- .NET数据库编程求索之路--5.使用ADO.NET实现(三层架构篇-使用List传递数据)(2)
- .NET数据库编程求索之路--6.使用ADO.NET实现(三层架构篇-使用List传递数据-基于存储过程)(2)