Qt 4.8: SQL Database Drivers

Qt Reference Documentation

- Qt 4.8
- ALL VERSIONS

- A
- A
- A
- Print

# SQL Database Drivers

The QtSql module uses driver plugins to communicate with the different database APIs. Since Qt's SQL Module API is database-independent, all database-specific code is contained within these drivers. Several drivers are supplied with Qt and other drivers can be added. The driver source code is supplied and can be used as a model for writing your own drivers.

## Supported Databases

The table below lists the drivers included with Qt. Due to license incompatibilities with the GPL, not all of the plugins are provided with Open Source Versions of Qt.

Driver name | DBMS
--- | ---
QDB2 | IBM DB2 (version 7.1 and above)
QIBASE | Borland InterBase
QMYSQL | MySQL
QOCI | Oracle Call Interface Driver
QODBC | Open Database Connectivity (ODBC) - Microsoft SQL Server and other ODBC-compliant databases
QPSQL | PostgreSQL (versions 7.3 and above)
QSQLITE2 | SQLite version 2
QSQLITE | SQLite version 3
QSYMSQL | SQLite version 3 for Symbian SQL Database
QTDS | Sybase Adaptive Server Note: obsolete from Qt 4.7

SQLite is the in-process database system with the best test coverage and support on all platforms. Oracle via OCI, and PostreSQL and MySQL through either ODBC or a native driver are well-tested on Windows and Linux. The completeness of the support for other systems depends on the availability and quality of client libraries.

Note: To build a driver plugin you need to have the appropriate client library for your Database Management System (DBMS). This provides access to the API exposed by the DBMS, and is typically shipped with it. Most installation programs also allow you to install "development libraries", and these are what you need. These libraries are responsible for the low-level communication with the DBMS.

## Building the Drivers Using Configure

On Unix and Mac OS X, the Qt `configure` script tries to automatically detect the available client libraries on your machine. Run `configure -help` to see what drivers can be built. You should get an output similar to this:

     -no-sql-<driver> ... Disable SQL <driver> entirely.
     -qt-sql-<driver> ... Enable a SQL <driver> in the Qt Library, by default
                          none are turned on.
     -plugin-sql-<driver> Enable SQL <driver> as a plugin to be linked to
                          at run time.

                          Possible values for <driver>:
                          [ db2 ibase mysql oci odbc psql sqlite sqlite2 tds ]

The `configure` script cannot detect the neccessary libraries and include files if they are not in the standard paths, so it may be necessary to specify these paths using the `-I` and `-L` command-line options. For example, if your MySQL include files are installed in `/usr/local/mysql` (or in `C:\mysql\include` on Windows), then pass the following parameter to configure: `-I/usr/local/mysql` (or `-I C:\mysql\include` for Windows).

On Windows the `-I` parameter doesn't accept spaces in filenames, so use the 8.3 name instead; for example, use `C:\progra~1\mysql` instead of `C:\Program Files\mysql`.

Use the `-qt-sql-<driver>` parameter to build the database driver statically into your Qt library or `-plugin-sql-<driver>` to build the driver as a plugin. Look at the sections that follow for additional information about required libraries.

## Building the Plugins Manually

### QMYSQL for MySQL 4 and higher

#### QMYSQL Stored Procedure Support

MySQL 5 introduces stored procedure support at the SQL level, but no API to control IN, OUT and INOUT parameters. Therefore, parameters have to be set and read using SQL commands instead of QSqlQuery::bindValue().

Example stored procedure:

     create procedure qtestproc (OUT param1 INT, OUT param2 INT)
     BEGIN
         set param1 = 42;
         set param2 = 43;
     END

Source code to access the OUT values:

     QSqlQuery q;
     q.exec("call qtestproc (@outval1, @outval2)");
     q.exec("select @outval1, @outval2");
     q.next();
     qDebug() << q.value(0) << q.value(1); // outputs "42" and "43"

Note: `@outval1` and `@outval2` are variables local to the current connection and will not be affected by queries sent from another host or connection.

#### Embedded MySQL Server

The MySQL embedded server is a drop-in replacement for the normal client library. With the embedded MySQL server, a MySQL server is not required to use MySQL functionality.

To use the embedded MySQL server, simply link the Qt plugin to `libmysqld` instead of libmysqlclient. This can be done by replacing `-lmysqlclient_r` by `-lmysqld` in the `qmake` command in the section below.

Please refer to the MySQL documentation, chapter "libmysqld, the Embedded MySQL Server Library" for more information about the MySQL embedded server.

#### How to Build the QMYSQL Plugin on Unix and Mac OS X

You need the MySQL header files and as well as the shared library `libmysqlclient.so`. Depending on your Linux distribution you may need to install a package which is usually called "mysql-devel".

Tell qmake where to find the MySQL header files and shared libraries (here it is assumed that MySQL is installed in `/usr/local`) and run `make`:

     cd $QTDIR/src/plugins/sqldrivers/mysql
     qmake "INCLUDEPATH+=/usr/local/include" "LIBS+=-L/usr/local/lib -lmysqlclient_r" mysql.pro
     make

After installing Qt, as described in the Installing Qt for X11 Platforms document, you also need to install the plugin in the standard location:

     cd $QTDIR/src/plugins/sqldrivers/mysql
     make install

#### How to Build the QMYSQL Plugin on Windows

You need to get the MySQL installation files. Run `SETUP.EXE` and choose "Custom Install". Install the "Libs & Include Files" Module. Build the plugin as follows (here it is assumed that MySQL is installed in `C:\MySQL`):

     cd %QTDIR%\src\plugins\sqldrivers\mysql
     qmake "INCLUDEPATH+=C:\MySQL\include" "LIBS+=C:\MYSQL\MySQL Server <version>\lib\opt\libmysql.lib" mysql.pro
     nmake

If you are not using a Microsoft compiler, replace `nmake` with `make` in the line above.

Note: This database plugin is not supported for Windows CE.

Note: Including `"-o Makefile"` as an argument to qmake to tell it where to build the makefile can cause the plugin to be built in release mode only. If you are expecting a debug version to be built as well, don't use the `"-o Makefile"` option.

#### How to build the MySQL driver for MinGW users

The following steps have been used successfully for WinXP SP3. In this example, Qt 4.6.2 is shown.

- Download the following components:
  - `MinGW-5.1.6.exe`
  - `mingw-utils-0.3.tar.gz`
  - Qt sources, e.g. `qt-everywhere-opensource-src-4.6.2.zip`
  - `mysql-5.1.35-win32.msi`
- Install `MinGW-5.1.6.exe` in, e.g. `C:\MinGW`.
- Extract `mingw-utils-0.3.tar.gz` into, e.g. `C:\MinGW`.
- Add the path for `MinGW-5.1.6.exe` to your `PATH` variable, e.g. `C:\MinGW\bin;`
- Extract the Qt sources, (`qt-everywhere-opensource-src-4.6.2.zip`), into, e.g. `C:\Qt`.
- Add the path for the eventual Qt binary to your `PATH` variable, e.g. `C:\Qt\4.6.2\bin;`.
- Install MySQL (`mysql-5.1.35-win32.msi`), customizing the components. Select only the headers and libraries. Install in, e.g. `C:\MySQL\MySQL51`.
- Open the DOS prompt, go to `C:\MySQL\MySQL51\lib\opt`, and run the following commands:
  - `reimp -d libmysql.lib`
  - `dlltool -k -d libmysql.def -l libmysql.a`
- Open the DOS prompt, go to `C:\Qt\4.6.2` and run the following commands:
  - `configure.exe -debug-and-release -platform win32-g++ -qt-sql-mysql -l mysql -I C:\MySQL\MySQL51\include -L C:\MySQL\MySQL51\lib\opt`
  - `mingw32-make sub-src`

  This step takes a long time.

- Open the DOS prompt, go to `C:\Qt\4.6.2\src\plugins\sqldrivers\mysql` and run the following command:
  - `qmake "INCLUDEPATH+=C:\MySQL\MySQL51\include" "LIBS+=-L. mysql" mysql.pro`
- Now the following libraries are ready in `C:\Qt\4.6.2\plugins\sqldrivers`.
  - `libqsqlmysql4.a`
  - `libqsqlmysqld4.a`
  - `qsqlmysql4.dll`
  - `qsqlmysqld4.dll`

  To use the SDK and QtCreator directly, copy these libraries to your `C:\Qt\...\qt\plugins\sqldrivers\`, and copy `C:\MySQL\MySQL51\lib\opt\libmysql.dll` to your `C:\Qt\...\qt\bin\`.

### QOCI for the Oracle Call Interface (OCI)

#### General Information about the OCI plugin

The Qt OCI plugin supports Oracle 9i, 10g and higher. After connecting to the Oracle server, the plugin will auto-detect the database version and enable features accordingly.

It's possible to connect to a Oracle database without a tnsnames.ora file. This requires that the database SID is passed to the driver as the database name and that a hostname is given.

#### OCI User Authentication

The Qt OCI plugin supports authentication using external credentials (OCI_CRED_EXT). Usually, this means that the database server will use the user authentication provided by the operating system instead of its own authentication mechanism.

Leave the username and password empty when opening a connection with QSqlDatabase to use the external credentials authentication.

#### OCI BLOB/LOB Support

Binary Large Objects (BLOBs) can be read and written, but be aware that this process may require a lot of memory. You should use a forward only query to select LOB fields (see QSqlQuery::setForwardOnly()).

Inserting BLOBs should be done using either a prepared query where the BLOBs are bound to placeholders or QSqlTableModel, which uses a prepared query to do this internally.

#### How to Build the OCI Plugin on Unix and Mac OS X

For Oracle 10g, all you need is the "Instant Client Package - Basic" and "Instant Client Package - SDK". For Oracle prior to 10g, you require the standard Oracle client and the SDK packages.

Oracle library files required to build the driver:

- `libclntsh.so` (all versions)
- `libwtc9.so` (only Oracle 9)

Tell `qmake` where to find the Oracle header files and shared libraries and run make:

For Oracle version 9:

     cd $QTDIR/src/plugins/sqldrivers/oci
     qmake "INCLUDEPATH+=$ORACLE_HOME/rdbms/public $ORACLE_HOME/rdbms/demo" "LIBS+=-L$ORACLE_HOME/lib -lclntsh -lwtc9" oci.pro
     make

For Oracle version 10, we assume that you installed the RPM packages of the Instant Client Package SDK (you need to adjust the version number accordingly):

     cd $QTDIR/src/plugins/sqldrivers/oci
     qmake "INCLUDEPATH+=/usr/include/oracle/10.1.0.3/client/" "LIBS+=-L/usr/lib/oracle/10.1.0.3/client/lib -lclntsh" oci.pro
     make

Note: If you are using the Oracle Instant Client package, you will need to set LD_LIBRARY_PATH when building the OCI SQL plugin and when running an applicaiton that uses the OCI SQL plugin. You can avoid this requirement by setting and RPATH and listing all of the libraries to link to. Here is an example:

     configure -I /usr/include/oracle/10.1.0.3/client -L /usr/lib/oracle/10.1.0.3/client/lib -R /usr/lib/oracle/10.1.0.3/client/lib -lclntsh -lnnz10
     make

If you wish to build the OCI plugin manually with this method the procedure looks like this:

     cd $QTDIR/src/plugins/sqldrivers/oci
     qmake "INCLUDEPATH+=/usr/include/oracle/10.1.0.3/client" "LIBS+=-L/usr/lib/oracle/10.1.0.3/client/lib -Wl,-rpath,/usr/lib/oracle/10.1.0.3/client/lib -lclntsh -lnnz10" oci.pro
     make

#### How to Build the OCI Plugin on Windows

Choosing the option "Programmer" in the Oracle Client Installer from the Oracle Client Installation CD is generally sufficient to build the plugin. For some versions of Oracle Client, you may also need to select the "Call Interface (OCI)" option if it is available.

Build the plugin as follows (here it is assumed that Oracle Client is installed in `C:\oracle`):

     set INCLUDE=%INCLUDE%;c:\oracle\oci\include
     set LIB=%LIB%;c:\oracle\oci\lib\msvc
     cd %QTDIR%\src\plugins\sqldrivers\oci
     qmake oci.pro
     nmake

If you are not using a Microsoft compiler, replace `nmake` with `make` in the line above.

When you run your application you will also need to add the `oci.dll` path to your `PATH` environment variable:

     set PATH=%PATH%;c:\oracle\bin

Note: This database plugin is not supported for Windows CE.

### QODBC for Open Database Connectivity (ODBC)

#### General Information about the ODBC plugin

ODBC is a general interface that allows you to connect to multiple DBMSs using a common interface. The QODBC driver allows you to connect to an ODBC driver manager and access the available data sources. Note that you also need to install and configure ODBC drivers for the ODBC driver manager that is installed on your system. The QODBC plugin then allows you to use these data sources in your Qt applications.

Note: You should use native drivers in preference to the ODBC driver where they are available. ODBC support can be used as a fallback for compliant databases if no native drivers are available.

On Windows an ODBC driver manager should be installed by default. For Unix systems there are some implementations which must be installed first. Note that every client that uses your application is required to have an ODBC driver manager installed, otherwise the QODBC plugin will not work.

Be aware that when connecting to an ODBC datasource you must pass in the name of the ODBC datasource to the QSqlDatabase::setDatabaseName() function rather than the actual database name.

The QODBC Plugin needs an ODBC compliant driver manager version 2.0 or later to work. Some ODBC drivers claim to be version 2.0 compliant, but do not offer all the necessary functionality. The QODBC plugin therefore checks whether the data source can be used after a connection has been established and refuses to work if the check fails. If you don't like this behavior, you can remove the `#define ODBC_CHECK_DRIVER` line from the file `qsql_odbc.cpp`. Do this at your own risk!

By default, Qt instructs the ODBC driver to behave as an ODBC 2.x driver. However, for some driver-manager/ODBC 3.x-driver combinations (e.g., unixODBC/MaxDB ODBC), telling the ODBC driver to behave as a 2.x driver can cause the driver plugin to have unexpected behavior. To avoid this problem, instruct the ODBC driver to behave as a 3.x driver by setting the connect option `"SQL_ATTR_ODBC_VERSION=SQL_OV_ODBC3"` before you open your database connection. Note that this will affect multiple aspects of ODBC driver behavior, e.g., the SQLSTATEs. Before setting this connect option, consult your ODBC documentation about behavior differences you can expect.

If you experience very slow access of the ODBC datasource, make sure that ODBC call tracing is turned off in the ODBC datasource manager.

Some drivers don't support scrollable cursors. In that case case only queries in forwardOnly mode can be used successfully.

#### ODBC Stored Procedure Support

With Microsoft SQL Server the result set returned by a stored procedure that uses the return statement, or returns multiple result sets, will be accessible only if you set the query's forward only mode to forward using QSqlQuery::setForwardOnly().

     // STORED_PROC uses the return statement or returns multiple result sets
     QSqlQuery query;
     query.setForwardOnly(true);
     query.exec("{call STORED_PROC}");

Note: The value returned by the stored procedure's return statement is discarded.

#### ODBC Unicode Support

The QODBC Plugin will use the Unicode API if UNICODE is defined. On Windows NT based systems, this is the default. Note that the ODBC driver and the DBMS must also support Unicode.

Some driver managers and drivers don't support UNICODE. To use the QODBC plugin with such drivers it has to be compiled with the Q_ODBC_VERSION_2 defined.

For the Oracle 9 ODBC driver (Windows), it is neccessary to check "SQL_WCHAR support" in the ODBC driver manager otherwise Oracle will convert all Unicode strings to local 8-bit.

#### How to Build the ODBC Plugin on Unix and Mac OS X

It is recommended that you use unixODBC. You can find the latest version and ODBC drivers at http://www.unixodbc.org. You need the unixODBC header files and shared libraries.

Tell `qmake` where to find the unixODBC header files and shared libraries (here it is assumed that unixODBC is installed in `/usr/local/unixODBC`) and run `make`:

     cd $QTDIR/src/plugins/sqldrivers/odbc
     qmake "INCLUDEPATH+=/usr/local/unixODBC/include" "LIBS+=-L/usr/local/unixODBC/lib -lodbc"
     make

#### How to Build the ODBC Plugin on Windows

The ODBC header and include files should already be installed in the right directories. You just have to build the plugin as follows:

     cd %QTDIR%\src\plugins\sqldrivers\odbc
     qmake odbc.pro
     nmake

If you are not using a Microsoft compiler, replace `nmake` with `make` in the line above.

Note: This database plugin is not officially supported for Windows CE.

### QPSQL for PostgreSQL (Version 7.3 and Above)

#### General Information about the QPSQL driver

The QPSQL driver supports version 7.3 and higher of the PostgreSQL server. We recommend that you use a client library from version 7.3.15, 7.4.13, 8.0.8, 8.1.4 or more recent as these versions contain security fixes, and as the QPSQL driver might not build with older versions of the client library depending on your platform.

For more information about PostgreSQL visit http://www.postgresql.org.

#### QPSQL Unicode Support

The QPSQL driver automatically detects whether the PostgreSQL database you are connecting to supports Unicode or not. Unicode is automatically used if the server supports it. Note that the driver only supports the UTF-8 encoding. If your database uses any other encoding, the server must be compiled with Unicode conversion support.

Unicode support was introduced in PostgreSQL version 7.1 and it will only work if both the server and the client library have been compiled with multibyte support. More information about how to set up a multibyte enabled PostgreSQL server can be found in the PostgreSQL Administrator Guide, Chapter 5.

#### QPSQL BLOB Support

Binary Large Objects are supported through the `BYTEA` field type in PostgreSQL server versions >= 7.1.

#### How to Build the QPSQL Plugin on Unix and Mac OS X

You need the PostgreSQL client library and headers installed.

To make `qmake` find the PostgreSQL header files and shared libraries, run `qmake` the following way (assuming that the PostgreSQL client is installed in `/usr`):

     cd $QTDIR/src/plugins/sqldrivers/psql
     qmake "INCLUDEPATH+=/usr/include/pgsql" "LIBS+=-L/usr/lib -lpq" psql.pro
     make

After installing Qt, as described in the Installing Qt for X11 Platforms document, you also need to install the plugin in the standard location:

     cd $QTDIR/src/plugins/sqldrivers/psql
     make install

#### How to Build the QPSQL Plugin on Windows

Install the appropriate PostgreSQL developer libraries for your compiler. Assuming that PostgreSQL was installed in `C:\psql`, build the plugin as follows:

     cd %QTDIR%\src\plugins\sqldrivers\psql
     qmake "INCLUDEPATH+=C:\psql\include" "LIBS+=C:\psql\lib\ms\libpq.lib" psql.pro
     nmake

Users of MinGW may wish to consult the following online document: PostgreSQL MinGW/Native Windows.

Note: This database plugin is not supported for Windows CE.

### QTDS for Sybase Adaptive Server

Note: TDS is no longer used by MS Sql Server, and is superceded by ODBC. QTDS is obsolete from Qt 4.7.

#### General Information about QTDS

It is not possible to set the port with QSqlDatabase::setPort() due to limitations in the Sybase client library. Refer to the Sybase documentation for information on how to set up a Sybase client configuration file to enable connections to databases on non-default ports.

#### How to Build the QTDS Plugin on Unix and Mac OS X

Under Unix, two libraries are available which support the TDS protocol:

- FreeTDS, a free implementation of the TDS protocol (http://www.freetds.org). Note that FreeTDS is not yet stable, so some functionality may not work as expected.
- Sybase Open Client, available from http://www.sybase.com. Note for Linux users: Get the Open Client RPM from http://linux.sybase.com.

Regardless of which library you use, the shared object file `libsybdb.so` is needed. Set the `SYBASE` environment variable to point to the directory where you installed the client library and execute `qmake`:

     cd $QTDIR/src/plugins/sqldrivers/tds
     qmake "INCLUDEPATH=$SYBASE/include" "LIBS=-L$SYBASE/lib -lsybdb"
     make

#### How to Build the QDTS Plugin on Windows

You can either use the DB-Library supplied by Microsoft or the Sybase Open Client (http://www.sybase.com). You must include `NTWDBLIB.LIB` to build the plugin:

     cd %QTDIR%\src\plugins\sqldrivers\tds
     qmake "LIBS+=NTWDBLIB.LIB" tds.pro
     nmake

By default the Microsoft library is used on Windows, if you want to force the use of the Sybase Open Client, you must define `Q_USE_SYBASE` in `%QTDIR%\src\sql\drivers\tds\qsql_tds.cpp`. If you are not using a Microsoft compiler, replace `nmake` with `make` in the line above.

Note: This database plugin is not supported for Windows CE.

### QDB2 for IBM DB2 (Version 7.1 and Above)

#### General Information about QDB2

The Qt DB2 plugin makes it possible to access IBM DB2 databases. It has been tested with IBM DB2 v7.1 and 7.2. You must install the IBM DB2 development client library, which contains the header and library files necessary for compiling the QDB2 plugin.

The QDB2 driver supports prepared queries, reading/writing of Unicode strings and reading/writing of BLOBs.

We suggest using a forward-only query when calling stored procedures in DB2 (see QSqlQuery::setForwardOnly()).

#### How to Build the QDB2 Plugin on Unix and Mac OS X

     cd $QTDIR/src/plugins/sqldrivers/db2
     qmake "INCLUDEPATH+=$DB2DIR/include" "LIBS+=-L$DB2DIR/lib -ldb2"
     make

After installing Qt, as described in the Installing Qt for X11 Platforms document, you also need to install the plugin in the standard location:

     cd $QTDIR/src/plugins/sqldrivers/db2
     make install

#### How to Build the QDB2 Plugin on Windows

The DB2 header and include files should already be installed in the right directories. You just have to build the plugin as follows:

     cd %QTDIR%\src\plugins\sqldrivers\db2
     qmake "INCLUDEPATH+=<DB2 home>/sqllib/include" "LIBS+=<DB2 home>/sqllib/lib/db2cli.lib"
     nmake

If you are not using a Microsoft compiler, replace `nmake` with `make` in the line above.

Note: This database plugin is not supported for Windows CE.

### QSQLITE2 for SQLite Version 2

The Qt SQLite 2 plugin is offered for compatibility. Whenever possible, use the version 3 plugin instead. The build instructions for version 3 apply to version 2 as well.

### QSQLITE for SQLite (Version 3 and Above)

#### General Information about QSQLITE

The Qt SQLite plugin makes it possible to access SQLite databases. SQLite is an in-process database, which means that it is not necessary to have a database server. SQLite operates on a single file, which must be set as the database name when opening a connection. If the file does not exist, SQLite will try to create it. SQLite also supports in-memory databases, simply pass ":memory:" as the database name.

SQLite has some restrictions regarding multiple users and multiple transactions. If you try to read/write on a resource from different transactions, your application might freeze until one transaction commits or rolls back. The Qt SQLite driver will retry to write to a locked resource until it runs into a timeout (see `QSQLITE_BUSY_TIMEOUT` at QSqlDatabase::setConnectOptions()).

In SQLite any column, with the exception of an INTEGER PRIMARY KEY column, may be used to store any type of value. For instance, a column declared as INTEGER may contain an integer value in one row and a text value in the next. This is due to SQLite associating the type of a value with the value itself rather than with the column it is stored in. A consequence of this is that the type returned by QSqlField::type() only indicates the field's recommended type. No assumption of the actual type should be made from this and the type of the individual values should be checked.

The driver is locked for updates while a select is executed. This may cause problems when using QSqlTableModel because Qt's item views fetch data as needed (with QSqlQuery::fetchMore() in the case of QSqlTableModel).

You can find information about SQLite on http://www.sqlite.org.

#### How to Build the QSQLITE Plugin

SQLite version 3 is included as a third-party library within Qt. It can be built by passing the following parameters to the configure script: `-plugin-sql-sqlite` (build as a plugin) or `-qt-sql-sqlite` (linked directly into the Qt library).

If you don't want to use the SQLite library included with Qt, you can build it manually (replace `$SQLITE` by the directory where SQLite resides):

     cd $QTDIR/src/plugins/sqldrivers/sqlite
     qmake "INCLUDEPATH+=$SQLITE/include" "LIBS+=-L$SQLITE/lib -lsqlite"
     make

After installing Qt, as described in the Installing Qt for X11 Platforms document, you also need to install the plugin in the standard location:

     cd $QTDIR/src/plugins/sqldrivers/sqlite
     make install

On Windows:

     cd %QTDIR%\src\plugins\sqldrivers\sqlite
     qmake "INCLUDEPATH+=C:\SQLITE\INCLUDE" "LIBS+=C:\SQLITE\LIB\SQLITE3.LIB" sqlite.pro
     nmake

#### QSQLITE File Format Compatibility

SQLite minor releases sometimes break file format forward compatibility. For example, SQLite 3.3 can read database files created with SQLite 3.2, but databases created with SQLite 3.3 cannot be read by SQLite 3.2. Please refer to the SQLite documentation and change logs for information about file format compatibility between versions.

Qt minor releases usually follow the SQLite minor releases, while Qt patch releases follow SQLite patch releases. Patch releases are therefore both backward and forward compatible.

To force SQLite to use a specific file format, it is neccessary to build and ship your own database plugin with your own SQLite library as illustrated above. Some versions of SQLite can be forced to write a specific file format by setting the `SQLITE_DEFAULT_FILE_FORMAT` define when building SQLite.

### QSYMSQL for SQLite (Version 3 and Above) with Symbian SQL Database

#### General Information about QSYMSQL

QSYMSQL driver enables clients to access the native Symbian database engine (�Symbian SQL�) through the QtSQL API.

The main difference to QSQLITE is that, with Symbian SQL database client can specify a set of access control policies when creating a new database. It uses Symbian SQL security policy definitions within open() call (security policy is defined with in the connection options parameters).

Symbian RSqlSecurityPolicy class is a container for the security policies for a shared SQL database.

The container can contain: security policies that apply to the database. security policies that apply to individual database objects, i.e. database tables.

For the database, you use RSqlSecurityPolicy::SetDbPolicy() to apply a separate security policy to: the database schema. read activity on the database. write activity on the database.

For database tables, you use RSqlSecurityPolicy::SetPolicy() to apply a separate security policy to: write activity on each named database table. read activity on each named database table.

More information about Symbian SQL and RSqlSecurityPolicy class reference about policy definitions, can be found from Forum Nokia Library: http://library.developer.nokia.com/.

Example of setting Security Policy:

Connection options hold definition for security policies and all parameters that does not contain "POLICY_" will be passed to RSqlDatabase. Policy will be filled according to parsed values.

Value in database wide parameters starts by definition which can be vendorId or secureId. These come directly from TSecurityPolicy class in Symbian.

POLICY_DB_DEFAULT Default security policy which will be used for the database and all database objects. POLICY_DB_DEFAULT must be defined before any other policy definitions can be used. POLICY_DB_READ Read database security policy. An application with read database security policy can read from database. POLICY_DB_WRITE: Write database security policy. An application with write database security policy can write to database. POLICY_DB_SCHEMA: Schema database security policy. An application with schema database security policy can modify the database schema, write to database, read from database.

Format: POLICY_DB_DEFAULT=cap1,cap2,cap3,cap4,cap5,cap6,cap7 (Up to 7 capabilities) POLICY_DB_READ=cap1,cap2,cap3,cap4,cap5,cap6,cap7 (Up to 7 capabilities) POLICY_DB_WRITE=vendorid,cap1,cap2,cap3 (Vendor ID and up to 3 capabilities) POLICY_DB_SCHEMA=secureid,cap1,cap2,cap3 (Secure ID and up to 3 capabilities)

Table policies does not support schema policy as database level does.

Table specific parameters would be as: POLICY_TABLE_WRITE=tablename,cap1,cap2,cap3,cap4,cap5,cap6,cap7 POLICY_TABLE_READ=tablename,cap1,cap2,cap3,cap4,cap5,cap6,cap7

Vendor Id and Secure id format: vid[0x12345678] (Hex) sid[0x12345678] (Hex)

Examples: Setting default policy: QSqlDatabase database = QSqlDatabase::addDatabase("QSYMSQL", "MyConnection"); database.setConnectOptions("POLICY_DB_DEFAULT=ReadDeviceData"); database.setDatabaseName("[12345678]myDatabase"); bool ok = database.open();

Setting POLICY_DB_WRITE: QSqlDatabase database = QSqlDatabase::addDatabase("QSYMSQL", "MyConnection"); database.setConnectOptions("POLICY_DB_DEFAULT=None; POLICY_DB_WRITE=sid[0x12345678], WriteDeviceData"); database.setDatabaseName("[12345678]myDatabase"); bool ok = database.open();

FOREIGN KEY: Enabling foreign key support from underlying SQLite add: "foreign_keys = ON" to your connection options string. This will be passes to SQLite.

Foreign key Example: QSqlDatabase database = QSqlDatabase::addDatabase("QSYMSQL", "MyConnection"); database.setDatabaseName("[12345678]myDatabase"); database.setConnectOptions("foreign_keys = ON"); bool ok = database.open();

#### How to Build the QSYMSQL Plugin

Building QSYMSQL requires Symbian SDK.

The build sequence is similar to the QSQLITE plugin with installing the plugin in the standard location.

Build sequence:

>cd sf`\mw``\qt``\src``\plugins``\sqldrivers``\symsql` >qmake >sbs -c winscw_udeb|armv5_urel

### QIBASE for Borland InterBase

#### General Information about QIBASE

The Qt InterBase plugin makes it possible to access the InterBase and Firebird databases. InterBase can either be used as a client/server or without a server in which case it operates on local files. The database file must exist before a connection can be established. Firebird must be used with a server configuration.

Note that InterBase requires you to specify the full path to the database file, no matter whether it is stored locally or on another server.

     db.setHostName("MyServer");
     db.setDatabaseName("C:\\test.gdb");

You need the InterBase/Firebird development headers and libraries to build this plugin.

Due to license incompatibilities with the GPL, users of the Qt Open Source Edition are not allowed to link this plugin to the commercial editions of InterBase. Please use Firebird or the free edition of InterBase.

#### QIBASE Unicode Support and Text Encoding

By default the driver connects to the database using UNICODE_FSS. This can be overridden by setting the ISC_DPB_LC_CTYPE parameter with QSqlDatabase::setConnectOptions() before opening the connection.

     // connect to database using the Latin-1 character set
     db.setConnectOptions("ISC_DPB_LC_CTYPE=Latin1");
     db.open();

If Qt doesn't support the given text encoding the driver will issue a warning message and connect to the database using UNICODE_FSS.

Note that if the text encoding set when connecting to the database is not the same as in the database, problems with transliteration might arise.

#### QIBASE Stored procedures

InterBase/Firebird return OUT values as result set, so when calling stored procedure, only IN values need to be bound via QSqlQuery::bindValue(). The RETURN/OUT values can be retrieved via QSqlQuery::value(). Example:

     QSqlQuery q;
     q.exec("execute procedure my_procedure");
     q.next();
     qDebug() << q.value(0); // outputs the first RETURN/OUT value

#### How to Build the QIBASE Plugin on Unix and Mac OS X

The following assumes InterBase or Firebird is installed in `/opt/interbase`:

If you are using InterBase:

     cd $QTDIR/src/plugins/sqldrivers/ibase
     qmake "INCLUDEPATH+=/opt/interbase/include" "LIBS+=-L/opt/interbase/lib" ibase.pro
     make

If you are using Firebird, the Firebird library has to be set explicitly:

     cd $QTDIR/src/plugins/sqldrivers/ibase
     qmake "INCLUDEPATH+=/opt/interbase/include" "LIBS+=-L/opt/interbase/lib -lfbclient" ibase.pro
     make

#### How to Build the QIBASE Plugin on Windows

The following assumes InterBase or Firebird is installed in `C:\interbase`:

If you are using InterBase:

     cd %QTDIR%\src\plugins\sqldrivers\ibase
     qmake "INCLUDEPATH+=C:\interbase\include" ibase.pro
     nmake

If you are using Firebird, the Firebird library has to be set explicitely:

     cd %QTDIR%\src\plugins\sqldrivers\ibase
     qmake "INCLUDEPATH+=C:\interbase\include" "LIBS+=-lfbclient" ibase.pro
     nmake

If you are not using a Microsoft compiler, replace `nmake` with `make` in the line above.

Note that `C:\interbase\bin` must be in the `PATH`.

Note: This database plugin is not supported for Windows CE.

## Troubleshooting

You should always use client libraries that have been compiled with the same compiler as you are using for your project. If you cannot get a source distibution to compile the client libraries yourself, you must make sure that the pre-compiled library is compatible with your compiler, otherwise you will get a lot of "undefined symbols" errors. Some compilers have tools to convert libraries, e.g. Borland ships the tool `COFF2OMF.EXE` to convert libraries that have been generated with Microsoft Visual C++.

If the compilation of a plugin succeeds but it cannot be loaded, make sure that the following requirements are met:

- Ensure that you are using a shared Qt library; you cannot use the plugins with a static build.
- Ensure that the plugin is in the correct directory. You can use QApplication::libraryPaths() to determine where Qt looks for plugins.
- Ensure that the client libraries of the DBMS are available on the system. On Unix, run the command `ldd` and pass the name of the plugin as parameter, for example `ldd libqsqlmysql.so`. You will get a warning if any of the client libraries couldn't be found. On Windows, you can use Visual Studio's dependency walker.
- Compile Qt with `QT_DEBUG_COMPONENT` defined to get very verbose debug output when loading plugins.

Make sure you have followed the guide to Deploying Plugins. If you experience plugin load problems and see output like this:

     QSqlDatabase: QMYSQL driver not loaded
     QSqlDatabase: available drivers: QMYSQL

the problem is usually that the plugin had the wrong build key. This might require removing an entry from the plugin cache.

## How to Write Your Own Database Driver

QSqlDatabase is responsible for loading and managing database driver plugins. When a database is added (see QSqlDatabase::addDatabase()), the appropriate driver plugin is loaded (using QSqlDriverPlugin). QSqlDatabase relies on the driver plugin to provide interfaces for QSqlDriver and QSqlResult.

QSqlDriver is an abstract base class which defines the functionality of a SQL database driver. This includes functions such as QSqlDriver::open() and QSqlDriver::close(). QSqlDriver is responsible for connecting to a database, establish the proper environment, etc. In addition, QSqlDriver can create QSqlQuery objects appropriate for the particular database API. QSqlDatabase forwards many of its function calls directly to QSqlDriver which provides the concrete implementation.

QSqlResult is an abstract base class which defines the functionality of a SQL database query. This includes statements such as `SELECT`, `UPDATE`, and `ALTER` `TABLE`. QSqlResult contains functions such as QSqlResult::next() and QSqlResult::value(). QSqlResult is responsible for sending queries to the database, returning result data, etc. QSqlQuery forwards many of its function calls directly to QSqlResult which provides the concrete implementation.

QSqlDriver and QSqlResult are closely connected. When implementing a Qt SQL driver, both of these classes must to be subclassed and the abstract virtual methods in each class must be implemented.

To implement a Qt SQL driver as a plugin (so that it is recognized and loaded by the Qt library at runtime), the driver must use the Q_EXPORT_PLUGIN2() macro. Read How to Create Qt Plugins for more information on this. You can also check out how this is done in the SQL plugins that are provided with Qt in `QTDIR/src/plugins/sqldrivers` and `QTDIR/src/sql/drivers`.

The following code can be used as a skeleton for a SQL driver:

     class XyzResult : public QSqlResult
     {
     public:
         XyzResult(const QSqlDriver *driver)
             : QSqlResult(driver) {}
         ~XyzResult() {}

     protected:
         QVariant data(int /* index */) { return QVariant(); }
         bool isNull(int /* index */) { return false; }
         bool reset(const QString & /* query */) { return false; }
         bool fetch(int /* index */) { return false; }
         bool fetchFirst() { return false; }
         bool fetchLast() { return false; }
         int size() { return 0; }
         int numRowsAffected() { return 0; }
         QSqlRecord record() const { return QSqlRecord(); }
     };

     class XyzDriver : public QSqlDriver
     {
     public:
         XyzDriver() {}
         ~XyzDriver() {}

         bool hasFeature(DriverFeature /* feature */) const { return false; }
         bool open(const QString & /* db */, const QString & /* user */,
                   const QString & /* password */, const QString & /* host */,
                   int /* port */, const QString & /* options */)
             { return false; }
         void close() {}
         QSqlResult *createResult() const { return new XyzResult(this); }
     };