Open Database Connectivity (ODBC) was developed to share data between heterogeneous databases. It has become a major component of the Windows Open System Architecture (WOSA) and a standard database access interface in Windows environments. ODBC provides a unified interface for accessing heterogeneous databases, allowing applications to access data managed by different database management systems (DBMSs) based on SQL. Therefore, applications can directly manipulate data in databases without requiring changes when the database changes. ODBC also allows you to access database files on various computers, as well as non-database objects such as Excel sheets and ASCII data files.
OceanBase Connector/ODBC is developed based on the MySQL ODBC driver. This driver allows you to use the new data models provided by OceanBase AI Database, such as the Array type. The following figure shows the application architecture of OceanBase Connector/ODBC.

Application
An application accesses data on an OBServer node by using a standard ODBC API. Then the ODBC API communicates with the driver manager. To access data, the application only needs to know the data source name (DSN), without knowing where or how the data is stored or how the system is configured.
The following tasks are common to all applications that use ODBC:
Select an OBServer node and connect.
Submit SQL statements for execution.
Retrieve results (if any).
Handle errors.
Commit or roll back transactions containing SQL statements.
Disconnect from the OBServer node.
Most data access operations are performed by using SQL statements. Therefore, applications that use OceanBase Connector/ODBC mainly need to submit SQL statements and retrieve the results generated by those statements.
Driver manager
The driver manager is a library that manages communication between applications and drivers. It mainly performs the following tasks:
Parses the DSN used to connect to the database. Database connection information is identified by the DSN. A DSN is a configuration string that identifies a given database driver, database, database host, and optional authentication information. Any ODBC-compatible application can use the same preconfigured DSN to connect to a data source.
Loads and unloads the drivers required for accessing the database defined in the DSN. For example, if you configure a DSN for connecting to OceanBase AI Database, the driver manager loads the OceanBase Connector/ODBC driver so that the ODBC API can communicate with the OBServer node.
Handles ODBC function calls or passes them to the driver.
OceanBase Connector/ODBC
OceanBase Connector/ODBC is a library that implements the functions supported by the ODBC API. It processes ODBC function calls, submits SQL requests to the OBServer node, and returns the results to the application. It can also modify application requests as needed to comply with the syntax specifications of OceanBase AI Database.
ODBC.INI
The ODBC.INI configuration file stores the driver and database information required for connecting to an OBServer node. Based on the DSN defined in ODBC.INI, the driver manager can determine which driver to load, and the driver can read the connection parameters.
OBServer node
An OBServer node stores the information of OceanBase AI Database. Query operations retrieve data from the database, and insert and update operations act on the data in the database.