mssql_free_result
Maybe it's unique to my FreeTDS configuration, but if I don't call mssql_free_statement() after every stored procedure (i.e. mssql_init, mssql_bind, mssql_execute, mssql_fetch_array), all subsequent stored procedures on the same database connection will fail.
I only mention it because this man-page deprecates the use of mssql_free_statement(), saying it's only there for run-time memory concerns. At least in my case, it's also a crucial step in the process of running a stored procedure. If anyone else has problems running multiple stored procedures on the same connection, I hope this helps them out.
mssql_free_statement
(PHP 4 >= 4.3.2, PHP 5, PECL odbtp:1.1.1-1.1.4)
mssql_free_statement — Free statement memory
Popis
bool mssql_free_statement
( resource $stmt
)
mssql_free_statement() only needs to be called if you are worried about using too much memory while your script is running. All statement memory will automatically be freed when the script ends. You may call mssql_free_statement() with the statement identifier as an argument and the associated statement memory will be freed.
Vrátené hodnoty
Vracia TRUE pri úspechu alebe FALSE pri chybe.
add a note
User Contributed Notesmssql_free_statement
mitch at 1800radiator dot kom
23-Mar-2005 10:02
23-Mar-2005 10:02