XCIV. ODBC Functions (Unified)
In addition to normal ODBC support, the Unified ODBC functions in
PHP allow you to access several databases that have borrowed the
semantics of the ODBC API to implement their own API. Instead of
maintaining multiple database drivers that were all nearly
identical, these drivers have been unified into a single set of
The following databases are supported by the Unified ODBC
functions: Adabas D,
Sybase SQL Anywhere.
There is no ODBC involved when connecting to the above
databases. The functions that you use to speak natively to them
just happen to share the same names and syntax as the ODBC
functions. The exception to this is iODBC. Building PHP with iODBC
support enables you to use any ODBC-compliant drivers with your PHP
applications. iODBC is maintained by
OpenLink Software. More information on iODBC, as well as a
HOWTO, is available at www.iodbc.org.
To access any of the supported databases you need to have
the required libraries installed.
Include Adabas D support. DIR is the Adabas base install directory,
defaults to /usr/local.
Include SAP DB support. DIR is SAP DB base install directory,
defaults to /usr/local.
Include Solid support. DIR is the Solid base install directory,
defaults to /usr/local/solid.
Include IBM DB2 support. DIR is the DB2 base install directory,
defaults to /home/db2inst1/sqllib.
Include Empress support. DIR is the Empress base install directory,
defaults to $EMPRESSPATH. From PHP 4, this option only supports
Empress Version 8.60 and above.
Include Empress Local Access support. DIR is the Empress base
install directory, defaults to $EMPRESSPATH. From PHP 4,
this option only supports Empress Version 8.60 and above.
Include Birdstep support. DIR is the Birdstep base install directory,
defaults to /usr/local/birdstep.
Include a user defined ODBC support. The DIR is ODBC install base directory,
which defaults to /usr/local. Make sure to define
CUSTOM_ODBC_LIBS and have some odbc.h in your include
dirs. E.g., you should define following for Sybase SQL Anywhere 5.5.00 on
QNX, prior to run configure script:
Include iODBC support. DIR is the iODBC base install directory,
defaults to /usr/local.
Include Easysoft OOB support. DIR is the OOB base install directory,
defaults to /usr/local/easysoft/oob/client.
Include unixODBC support. DIR is the unixODBC base install directory,
defaults to /usr/local.
Include OpenLink ODBC support. DIR is the OpenLink base install directory,
defaults to /usr/local. This is the same as iODBC.
Include DBMaker support. DIR is the DBMaker base install directory,
defaults to where the latest version of DBMaker is installed
(such as /home/dbmaker/3.6).
To disable unified ODBC support in PHP 3 add
--disable-unified-odbc to your configure
line. Only applicable if iODBC, Adabas, Solid, Velocis or a custom ODBC
interface is enabled.
PHP 的 Windows
这些函数的行为受 php.ini 的影响。
表格 1. Unified ODBC Configuration Options
|odbc.default_db *||NULL||PHP_INI_ALL|| |
|odbc.default_user *||NULL||PHP_INI_ALL|| |
|odbc.default_pw *||NULL||PHP_INI_ALL|| |
Entries marked with * are not implemented yet.
有关 PHP_INI_* 常量进一步的细节与定义参见附录 G
ODBC data source to use if none is specified in
User name to use if none is specified in
Password to use if none is specified in
Whether to allow persistent ODBC connections.
Check that a connection is still valid before reuse.
The maximum number of persistent ODBC connections per process.
The maximum number of ODBC connections per process, including
Handling of LONG fields. Specifies the number of bytes returned to
Handling of binary data.
I had big performance problems retrieving data form MS SQL Server with odbc only when the query was unsing a join.
I found out, that I had to connect with the cursor-type "SQL_CUR_USE_ODBC" and everything was ok:
$conn = odbc_connect("ShopLive", 'shop', 'xxx', SQL_CUR_USE_ODBC);
sven at ajaxtechforums dot com
I found this to be a perfect alternative to the MaxDB special drivers of version 7.5.00. Just weren't that easy to install on *nix. Windows seems fine. Anyway The ODBC is a perfect alternative for connecting the SAPDB/MaxDB towards PHP.
Installation guide for the odbc alternative (instead of the MAXDB-php driver) can be found here:
xangelusx at hotmail dot com
If you receive an error stating "Connection is busy with results for another hstmt, SQL state S1000 in SQLExecDirect" try opening your odbc connection using the SQL_CURSOR_FORWARD_ONLY option
$db_link = odbc_connect($dsn, $username, $password, SQL_CURSOR_FORWARD_ONLY)
or die('Error connecting to server. Server says: '.htmlspecialchars(odbc_errormsg()));
In response to Holger's comment about using @@identity:
Be carefull. If the table you're inserting into has a trigger that also inserts into another table that has an identity column you'll get the key of that other table! use scope_identity() instead of @@identity
I searched for the solution of why odbc connection of a network remote drive under Windows + Apache 2.0.X, cannot give the query, but seems no one provides the solution.
In fact, it is very simple.
Go to Control Panal -> Services;
Find and double click "Apache2";
In the page of "Log On", choose Log on as "This account" and give an account in the web server system which have the right to control the network remote drive;
Finally, restart Apache, and that's it.
denials at gmail dot com
Ever wonder why you're experiencing really slow data retrieval times using IBM DB2 Universal Database for Linux, UNIX, and Windows? The default cursor type used by Unified ODBC is not supported by DB2, so it gets downgraded to a forward-only cursor -- and that negotiation occurs with every row fetch.
One way to force your PHP applications to use forward-only cursors is to modify your DB2 client configuration with a handy CLI patch2 setting value of 6:
$ db2 UPDATE CLI CONFIGURATION FOR SECTION dbname USING patch2 6
You have to update this client setting on the same machine on which you are running the PHP application. This works on Windows operating systems as well as on Linux & UNIX operating systems.
I ran a few basic benchmarks (fetch 10,000 rows consisting of 3 INTEGER columns from a remote database server) and concluded that this setting can make a major difference to your application speed:
Without CLI patch2 setting: ~22 seconds
With CLI patch2 setting: ~ 1.75 seconds
Note that the drawback of using this patch setting (or any other method of using forward-only cursors) makes odbc_num_rows() always return "-1" for the number of rows affected by a SELECT statement.
pascals at NOSPAM dot pobox dot com
If the bundled ODBC library stumbles on some field formats (like some REAL from Pervasive.SQL), have a look at http://odbtp.sourceforge.net/.
After many headaches, I have adoped odbtp: it's a very solid library and best of all it's not tied to a particular OS.
vbwebprofi at gmx dot de
On my search for a function to retriew the NewID of an inserted row wich has an autoincrement I found this solution like the mysql_insert_id for an ODBC connection to MS-Access :
// make your connection below
$Connection = odbc_connect(...);
$Result = odbc_exec($Connection, "select @@identity");
$NewID = odbc_result($Result, 1);
// make here all what you want with the NewID
In my mind this should also work with MS-SQL-Server and with Sybase - via ODBC and direct (mssql_.../sybase_...).
dan dot polansky at seznam dot cz
First I just repeat that examples are here:
Second: Despite confusing remarks above, using unified ODBC functions you can really connect to any database for which you create DSN (Data Source Name). That is: using unified ODBC functions you can connect to _any_ database for which you have ODBC driver. Drivers exists or example Interbase, VisualFoxPro, DBase III,IV,V etc, many drivers are part of Win98 installation, other can be obtained from companies like EasySoft and Merant. ODBC is one of the most flexible ways for connecting to databases. This is because ODBC driver exist for almost every database there is. The question is, whether the driver is free. At least there are many 30 days trial versions of drivers.