I found that using odbc_close($odbchandle) on a connection opened by odbc_pconnect() causes a warning "not a valid ODBC-Link resource". So you can't just change odbc_connect() to odbc_pconnect() and expect things to work without warning messages. However, you can use odbc_close_all() and not get a warning.
odbc_pconnect
(PHP 4, PHP 5, PHP 7, PHP 8)
odbc_pconnect — Открывает постоянное соединение с базой данных
Описание
odbc_pconnect(
string
string
string
int
): resource|false
string
$dsn,string
$user,string
$password,int
$cursor_option = SQL_CUR_USE_DRIVER): resource|false
Открывает постоянное соединение с базой данных.
Функция очень похожа на odbc_connect(), за исключением
того, что соединение на самом деле не закрывается после завершения работы
скрипта. Последующие запросы на соединение с той же комбинацией
dsn, user и
password (с помощью odbc_connect()
и odbc_pconnect()) могут повторно использовать постоянное
соединение.
Список параметров
Для более подробной информации стоит обратиться к описанию odbc_connect().
Возвращаемые значения
Возвращает соединение ODBC или false в случае возникновения ошибки.
Примечания
Замечание: Постоянные соединения не действуют, если PHP используется как CGI.
add a note
User Contributed Notes 4 notes
wls at wwco dot com ¶
21 years ago
etsai at email dot com ¶
21 years ago
The following constants are defined for cursortype:
- SQL_CUR_USE_IF_NEEDED
- SQL_CUR_USE_ODBC
- SQL_CUR_USE_DRIVER
- SQL_CUR_DEFAULT
With some ODBC drivers, executing a complex stored procedure may fail with an error similar to: "Cannot open a cursor on a stored procedure that has anything other than a single select statement in it". Using SQL_CUR_USE_ODBC may avoid that error. Also, some drivers don't support the optional row_number parameter in odbc_fetch_row(). SQL_CUR_USE_ODBC might help in that case, too.
j_schrab at execpc dot com ¶
21 years ago
Ok, learning time. As I was told by the PHP-DevTeam...
Multiple connections are supported, but when you try to connect with exactly the same parameters, an existing
connection will be reused, leading to the behaviour you see.
You can simply omit the calls to odbc_close() since
connections get closed on script termination anyway or better:
Consider making your connection id a global variable or pass
it to your functions.
alberici at to dot infn dot it ¶
19 years ago
I saw that closing an ODBC persistent connection opened with odbc_pconnect() with odbc_close() doesnt work. Someone here have proposed using odbc_close_all() but wouldnt that close all persistent connections (also others ones !!!) ? What about catching a persistent handle with odbc_connect() and then closing the connection with odbc_close() ? If there are no available handles (for some reason the last pconn has been closed) this approach opens and close a normal single-script connection. Waiting comments...
