数据库编程经历（国外英文资料）.docVIP

数据库编程经验（国外英文资料） OLE DB and ADO 2.5 are both programming interfaces that provide common data access methods that are not relevant to the database server. OLE DB is a programming interface that applies the theoretical concepts of Microsoft universal data access (UDA) policies to practice. UDA is able to access various types of data through a COM based single programming interface, including relational, non-relational, and hierarchical data. OLE DB is designed as a component technology that features multiple layers of models. On one side of the COM bridge is the server component for keeping the data, and the other is the client component that knows how to connect and request data. The former is called the OLE DB data provider; The latter is called OLE DB users. Both the consumer and the provider are COM objects and can communicate with each other through a COM interface. This COM based communication can be summarized as operations performed on abstract objects such as DataSource, Session, Command, and Rowset. This occurs when the consumer connects to the DataSource, opens the Session, sends Command, and returns the data Rowset. The evolution of the ODBC UDA and OLE DB added a function, the function as a simple relational tables, all enterprise data together, whether they are structured relational and non-relational or level. OLE DB relies less on data physical structures than ODBC. In addition, it doesnt have to be strictly based on SQL. The OLE DB command can be an SQL statement or something else. In general, they can be thought of as text strings written in any syntax that can be understood by the target provider. Like ODBC, OLE DB is designed with the concept of c + + to maximize the performance of the mid-tier module data access. For the same reason, OLE DB cant be directly in Visual Basic? Use in ASP. And countless distributed systems generate components using Visual Basic. This is Microsoft introducing ActiveX? The main reason for the data object (ADO) library.