AnyDAC Architecture
From RemObjects Software
This is the AnyDAC Architecture reference page
Feel free to add your links to other appropriate new or existing topics below.
Contents |
Non visible Components [Comp]
The layer represents the AnyDAC public interfaces as Delphi non-visual components, similar to other Delphi data access components. It includes components - TADConnection (establish connection), TADQuery (execute query), TADStoredProc ( edecute stored procedure), etc. Main units are:
- uADCompDataSet;
- uADCompClient;
Visible Components [GUIx]
The layer provides a way to interact with the end user from an AnyDAC application. It is a set of high-level components allowing to add the end user dialogs for the standard database operations, like a Login or a Wait-for-operation. It includes components - TADGUIxWaitCursor (wait cursor), TADGUIxFormsQBldrDialog (query builder dialog), etc.
Local Data Storage [DatS]
The layer is a Local Data Storage implementation, which is analogue to the ADO.Net's DataSet and its related objects (DataTable, DataRow, DataView, etc). It is an in-memory data engine, actually storing and handling all client data and meta-data.
Data Adapter [DApt]
The layer allows automation and fine-tuning of a read operation with complex result sets (master-details, nested, ADT, etc) and allows posting updates back to the database system. It is controlled mostly through TField and UpdateOptions properites.
Debug and Performance Monitor [Moni]
The layer provides AnyDAC software-debugging capabilities. More precisely, it implements debug monitor interfaces, which allow monitoring the interaction between AnyDAC application and the DBMS. It is controlled mostly through [ADSettings] parameters of ADConnectionDefs.ini.
Drivers
The layer defines interfaces for physical data access. It implements them in a separate packages as drivers, whereas each driver package belongs to the Phys layer and implements the required interfaces using appropriate DBMS API. See Connections for connectivity details.
Native Drivers [Phys]
The native drivers are implementing access to a DBMS using a recomended by DBMS vendor high perfromance low-level API. Also, they precisely adapts DBMS specific features to AnyDAC API.
Bridging Drivers [Phys]
The briding drivers are implementing access to a DBMS using generic data access API's - ODBC and dbExpress. The briding drivers are using a driver suplied information regarding DBMS features, which is not covering all DBMS features interesting to AnyDAC.
Glossary — Features — How To — Components — Tools — Samples — Articles — Architecture — Issues
