When processing queries that return MANY rows, and when you put a limit on the number of rows you fetch from the result set, you should always call this function to close the current result set, because the SQL server may still be pending waiting for other rows to be fetched by your script. When you call this function, the Sybase client in PHP3 will signal to Sybase SQL Server that other pending results can be ignored, and the SQL server connection will return faster to the "waiting command" state, instead of keeping in the "suspend" state, saving much resources on the SQL-Server. In fact, it is a good idea to call this function after all your queries to save up SQL server resources.
Note that when processing SQL batchs with multiple queries, and stored procedure calls that return multiple result sets, there's no provision here to let the server return the next result set. There should be another function like sybase_next_result() to close the current result set, and let the SQL server go on the next SQL statements. Such a function would return a status that indicates if further results are coming or if the query is really terminated.
sybase_free_result
(PHP 4, PHP 5)
sybase_free_result — Libère un résultat Sybase de la mémoire
Avertissement
Cette fonction a été SUPPRIMÉE à partir de PHP 7.0.0.
Description
sybase_free_result
( resource
$result
) : boolsybase_free_result() n'est vraiment utile que si vous risquez d'utiliser trop de mémoire durant votre script. La mémoire occupée par les résultats est automatiquement libérée à la fin du script. Vous devez utiliser sybase_free_result() avec un identifiant de résultat et la mémoire utilisée par celui-ci sera libérée.
Liste de paramètres
-
result -
Valeurs de retour
Cette fonction retourne TRUE en cas de succès ou FALSE si une erreur survient.
add a note
User Contributed Notes 1 note
verdy_p at wanadoo dot fr ¶
24 years ago
