Supported Database Engines
- 3 minutes to read
The ExpressEntityMapping Framework provides access to data stores using database engines (also called database systems or DBMSs). The following table lists supported DBMS versions along with compatible provider/driver versions for dbGo ADO data access components.
Database Engine | Database Engine Version(s) | Compatible Driver/Provider Version(s) | Usage Notes |
|---|---|---|---|
Firebird | Firebird 1.5, Firebird 2.5.7 (with SQL dialect 3) | Firebird/InterBase ODBC driver v2.0.1 | The ExpressEntityMapping Framework is set to open an existing Firebird database. To create a Firebird database using the CreateSchema procedure of a session component connected to a FireDAC connection object (TFDConnection), set the object’s Params.OpenMode property to omOpenOrCreate. If you’re connecting to the database using a TADOConnection object, use the Firebird Interactive SQL utility (ISQL) available in the Firebird installation or other DB administration tools, such as IBExpert or FBExplorer, to create the database. Boolean type fields/properties are mapped to Char type columns containing 0 or 1 corresponding to False and True, respectively. The following applies to FireDAC connection objects only. Column names in tables are case-sensitive – mapped fields and properties in entity classes must match them. Key columns must be in the upper case. |
Microsoft Access | Microsoft Access 95-2003 | Microsoft Jet ODBC driver version 3 or later for 32-bit applications | FireDAC connection objects do not support foreign keys. |
Microsoft Access 95-2010 | Microsoft Jet ODBC driver version 12 or later for 32-bit and 64-bit applications | ||
Microsoft SQL Server | Microsoft SQL Server 7.0, SQL Server 2000, SQL Server 2000 Desktop Engine (MSDE 2000), SQL Server 2005, SQL Server 2005 Express Edition, SQL Server 2008, SQL Azure Database, SQL Server 2008 R2, SQL Server 2008 R2 Express, SQL Server 2012, SQL Server 2012 Express (including LocalDB), SQL Server 2014, SQL Server 2014 Express (including LocalDB), SQL Server 2016, SQL Server 2016 Express (including LocalDB) | Microsoft OLE DB provider for SQL Server | |
MySQL | MySQL Server 4.1, MySQL Server 5.0, MySQL Server 5.1, MySQL Server 5.7 | MySQL Connector/ODBC v5.1 driver | The ExpressEntityMapping Framework cannot create a MySQL database. To create it, use DB administration tools or execute corresponding SQL statements on the database side. Boolean type fields/properties are mapped to bit type columns. The following applies to ADO connection objects only. Install the Unicode version of the ODBC driver to be able to manipulate Unicode strings. |
Oracle | Oracle 9i, Oracle 10g, Oracle 11g, Oracle 12c | OraOLEDB.Oracle.1 provider for OLE DB | Table/column names in tables are case-sensitive – mapped entity classes, fields, and properties must match them. String type columns whose size exceeds 2000 characters cannot be manipulated using entity objects. Boolean type fields/properties are mapped to columns containing 0 or 1 corresponding to False and True, respectively. The following applies to FireDAC connection objects only. Key columns must be in the upper case. |
SQLite | SQLite 3 | SQLite3 ODBC driver v0.99 Note There’s a known driver issue with reading BLOB data. | String manipulation functions are not supported. When accessing a data store using FireDAC connection objects, you can work around this limitation by implementing equivalent functions and registering them as custom functions (TFDSQLiteFunction objects). Refer to the TfrmEMFCustomTutorial.RegisterSQLiteFunctions procedure in demos shipped with the ExpressEntityMapping Framework for an example of how to enable the use of a CharIndex function equivalent. |
Refer to the Connecting to a Data Store topic for details on how to connect to a specific data store.