Online Documentation
The following sections are available here:
Instructions
for Compiling SQLAPI++
Generally SQLAPI++ ships only with some release libraries
already compiled. We always recommend you recompile SQLAPI++
with the C++ compiler you use for your project/application. You should
use appropriate batch or makefiles located in the src
subdirectory of SQLAPI++ distributions.
Instructions
for Compiling and Linking Applications with SQLAPI++
SQLAPI++ programs need the following components of the
SQLAPI++ distribution:
Header files - Compile time
Programmers need to include the SQLAPI++ header files. Those
with a command-line compiler will typically use options such as
/I%SQLAPIDIR%\include or -I${SQLAPIDIR}/include. The header files are
in the include subdirectory of SQLAPI++ distributions:
#include <SQLAPI.h> - main header, should
be used whenever SQLAPI++ is used.
#include <ora7API.h>, <oraAPI.h> -
Oracle API, should be included if direct OCI calls are required
#include <ssOleDbAPI.h> - SQLServer API,
should be included if direct OLE DB calls are required
#include <ss6API.h> - SQLServer API,
should be included if direct DB-Library calls are required
#include <db2API.h> - DB2 API, should be
included if direct DB2 CLI calls are required
#include <infAPI.h> - Informix API,
should be included if direct Informix CLI calls are required
#include <ibAPI.h> - Interbase API,
should be included if direct InterBase API calls are required
#include <sbAPI.h> - SQLBase, should be
included if direct CAPI calls are required
#include <sybAPI.h> - Sybase, should be
included if direct Open Client calls are required
#include <myAPI.h> - MySQL, should be
included if direct MySQL C API calls are required
#include <pgAPI.h> - PostgreSQL, should
be included if direct libpq calls are required
#include <odbcAPI.h> - ODBC API, should
be included if direct ODBC API calls are required
#include <sl3API.h> - SQLite API, should
be included if direct SQLite API calls are required
Static or dynamic libraries - Link time
Programmers need to link with static or dynamic libraries.
Those with a command-line compiler will typically use options such as:
/L%SQLAPIDIR%\lib\sqlapi.lib.
The libraries are in the lib subdirectory of
SQLAPI++ distributions:
Win32:
sqlapi.lib - for linking with release version
of dynamic library (MSVC)
sqlapid.lib - for linking with debug version of
dynamic library (MSVC)
sqlapis.lib - for linking with release version
of static library (MSVC)
sqlapisd.lib - for linking with debug version
of static library (MSVC)
sqlapib.lib - for linking with release version
of dynamic library (Borland C++)
sqlapibd.lib - for linking with debug version
of dynamic library (Borland C++)
sqlapibs.lib - for linking with release
version of static library (Borland C++)
sqlapibsd.lib - for linking with debug version
of static library (Borland C++)
Linux/Unix:
libsqlapi.so - for linking with release version
of dynamic library (GNU C and C++ project compiler)
libsqlapid.so - for linking with debug version
of dynamic library (GNU C and C++ project compiler)
libsqlapi.a - for linking with release version
of static library (GNU C and C++ project compiler)
libsqlapid.a - for linking with debug version
of static library (GNU C and C++ project compiler)
Dynamic Link Libraries (DLLs) - Run time
Users of programs built with the dynamic SQLAPI++ libraries
need these same dynamic libraries to run the programs. The DLLs are in
the bin subdirectory of SQLAPI++ distributions:
Win32:
sqlapi.dll - for programs linked with the
release version of dynamic library (Microsoft VC++).
sqlapid.dll - for programs linked with the
debug version of dynamic library (Microsoft VC++).
sqlapib.dll - this is
release DLL for Borland C++.
sqlapibd.dll - this is debug DLL for Borland
C++.
Linux/Unix:
libsqlapi.so - for programs linked with the
release version of dynamic library (GNU C and C++ project compiler).
libsqlapid.so - for programs linked with the
debug version of dynamic library (GNU C and C++ project compiler).
Dynamic libraries are made available to programs in places
such as c:\windows\system on Windows platforms, in current folder or in
the path.
SQLAPI++ Class
Library Reference
SQLAPI++ allows to work with a number of SQL
database servers. It provides common mechanisms to access database, and
as a general rule they work for any database server. But each server
has some specific features which a developer has to
know in order to leverage server's unique features and avoid potential
errors.
In the following topics we tried to collect all specific
information that concerns working with each server supported by
SQLAPI++ Library. Full information about using SQLAPI++ see in How To and Online Documentation.
Available DBMS:
Last modified: 29 January 2008
webmaster@sqlapi.com
|