odbc_num_rows
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...
odbc_pconnect
(PHP 4, PHP 5)
odbc_pconnect — Abre uma conexão persistente com o servidor de banco de dados
Descrição
resource odbc_pconnect
( string $dsn
, string $user
, string $password
[, int $cursor_type
] )
Retorna uma id de conexão ODBC ou 0 (FALSE) em caso de erro. Esta função é muito parecida com odbc_connect(), exceto que a conexão não é realmente fechada quando o script termina. Requisições futuras com o mesma combinação de dsn , user , password (via odbc_connect() e odbc_pconnect()) podem reutilizar a conexão persistente.
Nota: Conexões persistentes não tem efeito se o PHP é utilizado como um programa CGI.
Para informações sobre o parâmetro opcional cursor_type veja a função odbc_connect(). Para maiores informações sobre as conexões persistentes, leia o FAQ PHP.
add a note
User Contributed Notesodbc_pconnect
alberici at to dot infn dot it
15-Jul-2002 01:42
15-Jul-2002 01:42
j_schrab at execpc dot com
16-Jan-2001 06:41
16-Jan-2001 06:41
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.
wls at wwco dot com
11-Aug-2000 04:44
11-Aug-2000 04:44
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.
etsai at email dot com
29-Jun-2000 06:10
29-Jun-2000 06:10
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.