| Home | All Classes | Main Classes | Annotated | Grouped Classes | Functions | |
The SQL Module uses driver plugins in order to communicate with different database APIs. Since the SQL Module API is database-independent, all database-specific code is contained within these drivers. Several drivers are supplied with TQt and other drivers can be added. The driver source code is supplied and can be used as a model for writing your own drivers.
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.
The drivers shipped with TQt are:
Note that not all of the plugins are shipped with the TQt Open Source Edition due to license incompatibilities with the GPL.
The TQt configure script automatically detects 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:
Possible values for <driver>: [ mysql oci odbc psql tds ] Auto-Detected on this system: [ mysql psql ]
Note that on Windows, the configure script doesn't do any auto-detection.
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" switches. For example, if your MySQL include files are installed in /usr/local/mysql (or in C:\mysql\include configure: -I/usr/local/mysql (or -I C:\mysql\include Windows).
On Windows the -I parameter doesn't accept spaces in filenames, so use the 8.3 name instead, i.e. 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 TQt library or -plugin-sql-<driver> to build the driver as a plugin. Look at the sections that follow for additional information about required libraries.
MySQL 3.x doesn't support SQL transactions by default. There are some backends which offer this functionality. Recent versions of the MySQL client libraries (>3.23.34) allow you to use transactions on those modified servers.
If you have a recent client library and connect to a transaction-enabled MySQL server, a call to the TQSqlDriver::hasFeature( TQSqlDriver::Transactions ) function returns TRUE and SQL transactions can be used.
If the plugin is compiled against MySQL 4.x client libraries, transactions are enabled by default.
You can find information about MySQL on http://www.mysql.com
You need the MySQL header files and as well as the shared library libmysqlclient.so. Depending on your Linux distribution you 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 $TQTDIR/plugins/src/sqldrivers/mysql qmake -o Makefile "INCLUDEPATH+=/usr/local/include" "LIBS+=-L/usr/local/lib -lmysqlclient" mysql.pro make
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 %TQTDIR%\plugins\src\sqldrivers\mysql qmake -o Makefile "INCLUDEPATH+=C:\MYSQL\INCLUDE" "LIBS+=C:\MYSQL\LIB\OPT\LIBMYSQL.LIB" mysql.pro nmake
If you are not using a Microsoft compiler, replace nmake with make in the statement above.
The TQt OCI plugin supports both Oracle 8 and Oracle 9. After connecting to the Oracle server, the plugin will auto-detect the database version and enable features accordingly.
If the Oracle server supports Unicode, the OCI plugin will use UTF-8 encoding to communicate with the server.
Binary Large Objects (BLOBs) can be read and written, but be aware that this process may require a lot of memory.
Note that Oracle 9 doesn't support scrollable result sets with LOB columns, you have to use a forward only query to select LOB fields (see TQSqlQuery::setForwardOnly()).
Inserting BLOBs should be done using either a prepared query where the BLOBs are bound to placeholders, or TQSqlCursor which uses a prepared query to do this internally (see $TQTDIR/examples/sql/blob).
When a query is in forward only mode a call to TQSqlQuery::last() will position the query on the last record and return TRUE, but subsequent calls to TQSqlQuery::value() will only return NULLs.
All files required to build driver should ship with the standard Oracle Client install.
Oracle library files required to build driver:
Tell qmake where to find the Oracle header files and shared libraries (it is assumed that the variable $ORACLE_HOME points to the directory where Oracle is installed) and run make:
If you are using Oracle 8:
cd $TQTDIR/plugins/src/sqldrivers/oci qmake -o Makefile "INCLUDEPATH+=$ORACLE_HOME/rdbms/public $ORACLE_HOME/rdbms/demo" "LIBS+=-L$ORACLE_HOME/lib -lclntsh -lwtc8" oci.pro make
For Oracle version 9:
cd $TQTDIR/plugins/src/sqldrivers/oci qmake -o Makefile "INCLUDEPATH+=$ORACLE_HOME/rdbms/public $ORACLE_HOME/rdbms/demo" "LIBS+=-L$ORACLE_HOME/lib -lclntsh -lwtc9" oci.pro make
For Oracle version 10:
cd $TQTDIR/plugins/src/sqldrivers/oci qmake -o Makefile "INCLUDEPATH+=$ORACLE_HOME/rdbms/public $ORACLE_HOME/rdbms/demo" "LIBS+=-L$ORACLE_HOME/lib -lclntsh" oci.pro make
Note that some versions of the OCI client libraries contain a bug that makes programs linked to these libraries segfault on exit. This only happens if the TQOCI8 driver is compiled as a plugin. To work around this problem, either compile the driver into the TQt libray itself, or configure TQt with the option '-DTQT_NO_LIBRARY_UNLOAD'. For Oracle 9, it is possible to link to the static OCI library by using "LIBS+=$ORACLE_HOME/lib/libclntst9.a".
Choosing the option "Programmer" in the Oracle Client Installer from the Oracle Client Installation CD is sufficient to build the plugin.
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 %TQTDIR%\plugins\src\sqldrivers\oci qmake -o Makefile oci.pro nmake
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
If you are not using a Microsoft compiler, replace nmake with make in the statement above.
ODBC is a general interface that allows you to connect to multiple DBMS using a common interface. The TQODBC3 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 TQODBC3 plugin then allows you to use these data sources in your TQt project.
On Windows systems after 95 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 TQODBC3 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 TQSqlDatabase::setDatabaseName() function: not the actual database name.
The TQODBC3 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 TQODBC3 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 behaviour, you can remove the #define ODBC_CHECK_DRIVER line from the file qsql_odbc.cpp. Do this at your own risk!
If you experience very slow access of the ODBC datasource, make sure that ODBC call tracing is turned off in the ODBC datasource manager.
The TQODBC3 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 have to support Unicode as well.
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.
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 $TQTDIR/plugins/src/sqldrivers/odbc qmake "INCLUDEPATH+=/usr/local/unixODBC/include" "LIBS+=-L/usr/local/unixODBC/lib -lodbc" make
The ODBC header and include files should already be installed in the right directories. You just have to build the plugin as follows:
cd %TQTDIR%\plugins\src\sqldrivers\odbc qmake -o Makefile odbc.pro nmake
If you are not using a Microsoft compiler, replace nmake with make in the statement above.
The TQPSQL7 driver supports both version 6 and 7 of PostgreSQL. We recommend compiling the plugin with a recent version of the PostgreSQL client library (libpq) because it is more stable and still backwards compatible.
If you want to link the plugin against the libpq shipped with version 6 we recommend a recent version like PostgreSQL 6.5.3, otherwise a connection to a version 7 server may not work.
The driver auto-detects the server version of PostgreSQL after a connection was successful. If the server is too old or the version information cannot be determined a warning is issued.
For more information about PostgreSQL visit http://www.postgresql.org.
The TQPSQL7 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.
Binary Large Objects are supported through the BYTEA field type in PostgreSQL versions >= 7.1. Fields of type OID can be read, but not written. Use the PostgreSQL command lo_import to insert binary data into OID fields.
Just installing the pq client library and the corresponding header files is not sufficient. You have to get the PostgreSQL source distribution and run the configure script. If you've already installed a binary distribution you don't need to build it. The source distribution is needed because the TQPSQL7 plugin relies on a couple of header files that are usually not a part of the binary distribution.
To make qmake find the PostgreSQL header files and shared libraries, run qmake the following way (assuming that the PostgreSQL sources can be found in /usr/src/psql):
cd $TQTDIR/plugins/src/sqldrivers/psql qmake -o Makefile "INCLUDEPATH+=/usr/src/psql/src/include /usr/src/psql/src/interfaces/libpq" "LIBS+=-L/usr/lib -lpq" psql.pro make
Unpack and build the PostgreSQL source distribution as described in the PostgreSQL documentation. Assuming the PostgreSQL sources resides in C:\psql, build the plugin as follows:
cd %TQTDIR%\plugins\src\sqldrivers\psql qmake -o Makefile "INCLUDEPATH+=C:\psql\src\include C:\psql\src\interfaces\libpq" psql.pro nmake
Remember to add the path to the libpq.dll library to your PATH environment variable so that Windows can find it. In this case that would be C:\psql\src\interfaces\libpq\Release. If you are not using a Microsoft compiler, replace nmake with make in the statement above.
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 $TQTDIR/plugins/src/sqldrivers/tds qmake -o Makefile "INCLUDEPATH=$SYBASE/include" "LIBS=-L$SYBASE/lib -lsybdb" make
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 %TQTDIR%\plugins\src\sqldrivers\tds qmake -o Makefile "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 %TQTDIR%\src\sql\drivers\tds\qsql_tds.cpp.
The TQt DB2 plugin makes it possible to access IBM DB2 databases. It has been tested with IBM DB2 v7.1 and 7.2. You have to install the IBM DB2 development client library, which contains the header and library files necessary for compiling the TQDB2 plugin.
The TQDB2 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 TQSqlQuery::setForwardOnly()).
cd $TQTDIR/plugins/src/sqldrivers/db2 qmake -o Makefile "INCLUDEPATH+=$DB2DIR/include" "LIBS+=-L$DB2DIR/lib -ldb2" make
The DB2 header and include files should already be installed in the right directories. You just have to build the plugin as follows:
cd %TQTDIR%\plugins\src\sqldrivers\db2 qmake -o Makefile "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 statement above.
The TQt SQLite plugin makes it possible to access SQLite databases. SQLite is an in-process database, meaning that it is not necessary to have a database server. SQLite operates on a single file, which has to be set as 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.
SQLite has no support for types, every value is treated as character data. BLOBs are therefore not supported.
You can find information about SQLite on http://www.sqlite.org.
SQLite is shipped as third party library within TQt. It can be built by passing the following parameters to the configure script: -plugin-sql-sqlite (as plugin) or -qt-sql-sqlite (linked directly into the TQt library).
If you don't want to use the SQLite library shipped with TQt, you can build it manually (replace $SQLITE by the directory where SQLite resides):
cd $TQTDIR/plugins/src/sqldrivers/sqlite qmake -o Makefile "INCLUDEPATH+=$SQLITE/include" "LIBS+=-L$SQLITE/lib -lsqlite" make
The TQt 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 operating on local files. The database file must exist before a connection can be established.
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.
myDatabase->setHostName("MyServer");
myDatabase->setDatabaseName("C:\\test.gdb");
You need the Interbase/Firebird development headers and libraries to build this plugin.
Due to the GPL, users of the TQt 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.
The following assumes Interbase or Firebird is installed in /opt/interbase:
cd $TQTDIR/plugins/src/sqldrivers/ibase qmake -o Makefile "INCLUDEPATH+=/opt/interbase/include" "LIBS+=-L/opt/interbase/lib" ibase.pro make
The following assumes Interbase or Firebird is installed in C:\interbase:
cd %TQTDIR%\plugins\src\sqldrivers\ibase qmake -o Makefile "INCLUDEPATH+=C:\interbase\include" ibase.pro nmake
If you are not using a Microsoft compiler, replace nmake with make in the statement above.
Note that C:\interbase\bin must be in the PATH.
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:
If you are experiencing problems with loading plugins, and see output like this
TQSqlDatabase warning: TQMYSQL3 driver not loaded TQSqlDatabase: available drivers: TQMYSQL3
the problem is probably that the plugin had the wrong build key. For debugging purposes, remove the corresponding entry in the $HOME/.qt/qt_plugins_(qtversion).rc file.
The next time you try to load this plugin, it will give you a more detailed error message.
TQSqlDatabase is responsible for loading and managing database driver plugins. When a database is added (see TQSqlDatabase::addDatabase()), the appropriate driver plugin is loaded (using TQSqlDriverPlugin). TQSqlDatabase relies on the driver plugin to provide interfaces for TQSqlDriver and TQSqlResult.
TQSqlDriver is an abstract base class which defines the functionality of a SQL database driver. This includes functions such as TQSqlDriver::open() and TQSqlDriver::close(). TQSqlDriver is responsible for connecting to a database, establish the proper environment, etc. In addition, TQSqlDriver can create TQSqlQuery objects appropriate for the particular database API. TQSqlDatabase forwards many of its function calls directly to TQSqlDriver which provides the concrete implementation.
TQSqlResult is an abstract base class which defines the functionality of a SQL database query. This includes statements such as SELECT, UPDATE, and ALTER TABLE. TQSqlResult contains functions such as TQSqlResult::next() and TQSqlResult::value(). TQSqlResult is responsible for sending queries to the database, returning result data, etc. TQSqlQuery forwards many of its function calls directly to TQSqlResult which provides the concrete implementation.
TQSqlDriver and TQSqlResult are closely connected. When implementing a TQt SQL driver, both of these classes must to be subclassed and the abstract virtual methods in each class must be implemented.
To implement a TQt SQL driver as a plugin (so that it is recognized and loaded by the TQt library at runtime), the driver must use the TQ_EXPORT_PLUGIN macro. Read the TQt Plugin documentation for more information on this. You can also check out how this is done in the SQL plugins that is provided with TQt in TQTDIR/plugins/src/sqldrivers and TQTDIR/src/sql/drivers.
The following code can be used as a skeleton for a SQL driver:
class TQNullResult : public TQSqlResult
{
public:
TQNullResult( const TQSqlDriver* d ): TQSqlResult( d ) {}
~TQNullResult() {}
protected:
TQVariant data( int ) { return TQVariant(); }
bool reset ( const TQString& ) { return FALSE; }
bool fetch( int ) { return FALSE; }
bool fetchFirst() { return FALSE; }
bool fetchLast() { return FALSE; }
bool isNull( int ) { return FALSE; }
TQSqlRecord record() { return TQSqlRecord(); }
int size() { return 0; }
int numRowsAffected() { return 0; }
};
class TQNullDriver : public TQSqlDriver
{
public:
TQNullDriver(): TQSqlDriver() {}
~TQNullDriver() {}
bool hasFeature( DriverFeature ) const { return FALSE; }
bool open( const TQString&,
const TQString&,
const TQString&,
const TQString&,
int ) { return FALSE; }
void close() {}
TQSqlQuery createQuery() const { return TQSqlQuery( new TQNullResult( this ) ); }
};
| Copyright © 2007 Trolltech | Trademarks | TQt 3.3.8
|