odbc_free_result

(PHP 4, PHP 5)

odbc_free_result — Liberar los recursos asociados con un resultado

Descripción

bool odbc_free_result ( resource $result_id )

Libera los recursos asociados con un resultado.

odbc_free_result() sólo necesita ser llamado si se tiene preocupación de usar demasiada memoria mientras se está ejecutando el script. Toda la memoria de resultados será liberada cuando el script finalice.

Parámetros

result_id: El identificador de resultado.

Valores devueltos

Siempre devuelve TRUE.

Notas

Nota:
Si el auto-envío está deshabilitado (véase odbc_autocommit()) y se llama a odbc_free_result() antes del envío, todas las transacciones pendientes serán reanudadas.

odbc_gettypeinfo

odbc_foreignkeys

[edit] Last updated: Fri, 17 May 2013

add a note User Contributed Notes odbc_free_result - [4 notes]

down

-1

EMY ¶

4 years ago


It seems it is common sense to say it is a god practice to free any resource when it isn´t necessary anymore.

Also, when talking about releasing the resources associated with a given result set it is a common sense to say never release a result set before it is assured to have been either commited or rolled back.

Then, the following code sequence should be the most adequate (assuming auto-commit is disabled):



odbc_commit(...);

odbc_free_result(...);

...

odbc_close(...);

down

-1

rich at kastle dot com ¶

8 years ago


("Note:  If auto-commit is disabled (see odbc_autocommit()) and you call odbc_free_result() before committing, all pending transactions are rolled back.")



I've looked thru the code, and that note is definitely wrong, at least in my environment (Windows/SQL Server).  odbc_free_result ultimately just calls SQLFreeStmt which has NO EFFECT on outstanding transactions.



In fact, it seems it must be wrong for all environments, because the SQLFreeStmt is bound to the destruction of the result resource.  So unset($result) would be just as dangerous - and you're randomly and unpredictably screwed if garbage collection reaps the result set before your transaction's done.

down

-1

rogersd at island dot net ¶

11 years ago


odbc_free_result() is also the way to avoid the dreaded "Too many open cursor" error.

down

-2

lm At bible in switzerland ¶

2 years ago


I use WinDev 15.0 HyperFileSQL ODBC Connector on Windows, PHP 5.2.3.

With this configuration, any result ressource obtained with odbc_exec must be freed by odbc_free_result before the next query by odbc_exec.

If the result ressource is not freed odbc_exec will return a corrupt result ressource.

example:

odbc_exec($query1);

odbc_exec($query2);

odbc_result_all();



Output: A table with empty cells

add a note