TSQLConnection is an abstract class representing a connection between a client program and a datastore through a database protocol. Connections are responsible for commands (TSQLCommand) and catalogs (TSQLTableCatalog, TSQLColumnCatalog). Providers must implement concrete subclasses derived from TSQLConnection. Client applications can either create a concrete subclass with all the public pure virtual member functions implemented, or use the default connection classes provided by the client interface. For more information about default connection classes, see TSQLStandardConnection.
TSQLConnectionHandle is a counted-pointer surrogate for TSQLConnection.
TSQLStandardConnection provides the client application with an implementation satisfying most connectivity needs. Clients should not use instances of this class directly, but should instead use instances of the counted-pointer surrogate TSQLStandardConnectionHandle. Providers with special connectivity needs can extend the SQLDAS framework as needed by deriving from TSQLConnection.
TSQLStandardConnectionHandle is a concrete class that is a counted-pointer surrogate for TSQLStandardConnection. Clients should use this class to create a standard connection.
TSQLProduct is a concrete class. Each instance describes a SQL product, such as a datastore or database access protocol. SQL product information is required to instantiate a connection. Clients should not use TSQLProduct directly. Instead, use member functions inherited through such derived classes as TSQLStandardDBProtocol and TSQLStandardDataStore.
TSQLDBProtocol is a concrete class that describes a database access protocol, such as SQL*Net. SQLDAS clients must use one of the TSQLStandardDBProtocol derived subclasses to specify a particular protocol. Derived subclasses currently include:
TSQLDataStore is a concrete class that describes a data store. This is typically a relational database such as Oracle 7, Sybase, and DB2. SQLDAS clients should make use of one of the derived subclasses to specify a particular database. To instantiate a database connection object, you are required to specify the database protocol. Derived subclasses of TSQLDataStore include:
TSQLLogonStep defines a unit of logon interaction in an extended logon sequence. Logging on to a database server in a client server environment might require multiple user and password pairs to pass the various layers of authentication required by different computer hosts and databases. The interpretation of a particular logon step is the responsibility of the connection object.
[Contents]
[Previous]
[Next]
Click the icon to mail questions or corrections about this material to Taligent personnel.