odbc_foreignkeys
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(...);
odbc_free_result
(PHP 4, PHP 5)
odbc_free_result — Libère les ressources associées à un résultat
Description
bool odbc_free_result
( resource $result_id
)
Libère les ressources associées à un résultat.
odbc_free_result() n'est nécessaire que si vous craignez d'utiliser trop de mémoire lors de l'exécution de votre script. Tous les résultats en mémoire seront libérés dès la fin du script.
Liste de paramètres
- result_id
-
L'identifiant de résultat.
Valeurs de retour
Retourne toujours TRUE.
Notes
Note: Si l'autovalidation est désactivée (voir odbc_autocommit()) et que vous appelez odbc_free_result() avant de valider vos requêtes, toutes les transactions préparées seront annulées.
add a note
User Contributed Notesodbc_free_result
EMY
03-Feb-2009 05:45
03-Feb-2009 05:45
rich at kastle dot com
20-Dec-2004 12:48
20-Dec-2004 12:48
("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.
rogersd at island dot net
06-Sep-2001 05:03
06-Sep-2001 05:03
odbc_free_result() is also the way to avoid the dreaded "Too many open cursor" error.