使用设计模式构建通用数据库访问类_C#（国外英文资料）.doc

使用设计模式构建通用数据库访问类_C#（国外英文资料） Build the generic database access class _C # using the design pattern In the design of the application, the database access is very important, we usually need to access to the database together, in order to assure good encapsulation and maintainability. I, database access, for Microsofts own used and other database (support the OleDb), different access methods, these classes are distributed in the System. The Data. SqlClient and System. Data. The OleDb namespace. Microsoft later introduced a library for accessing Oracle databases. We hope that at the time of writing application system, not affected by so many kind of different, can try to be database has nothing to do, when the backstage database is changed, dont need to change the client code. Sometimes, for performance and other reasons, we also want to provide cache of database access, especially for database connections. While Microsoft has built-in database caching for us, it is undoubtedly more flexible and efficient to control the cache. This will require us to do another encapsulation of these database access classes in the actual development process. Here, this is a real strategy that has a very good effect in practice. The Factory and Silgleton design patterns are the main methods used. Lets take a look at what Factory means: define an interface for creating objects, and let the subclass decide which class to instantiate. Factory Method delays the instantiation of a class to its subclasses. Here could we deal with for a variety of database operations, therefore, need to first define a manipulation of the database interface, and then, depending on the database, by the class is instantiated to decide which class factory. Next, lets define the access interface first. To illustrate the problem, weve defined fewer methods for this class, and other methods are easy to follow. Also note that I use the abstract class here to define the access interface, not the interface, for reasons yo