mssql_free_statement

Free statement memory (PHP 4 >= 4.3.2, PHP 5, PECL odbtp:1.1.1-1.1.4)
bool mssql_free_statement ( resource stmt )

Examples ( Source code ) » mssql_free_statement


<?php

// Create a new statement

$stmt = mssql_init('test');


// Bind values here and execute the statement


// once we're done, we clear it from the memory

// using mssql_free_statement like so:

mssql_free_statement($stmt);

?>

Code Examples / Notes » mssql_free_statement

mitch

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.

Change Language

mssql_bind
mssql_close
mssql_connect
mssql_data_seek
mssql_execute
mssql_fetch_array
mssql_fetch_assoc
mssql_fetch_batch
mssql_fetch_field
mssql_fetch_object
mssql_fetch_row
mssql_field_length
mssql_field_name
mssql_field_seek
mssql_field_type
mssql_free_result
mssql_free_statement
mssql_get_last_message
mssql_guid_string
mssql_init
mssql_min_error_severity
mssql_min_message_severity
mssql_next_result
mssql_num_fields
mssql_num_rows
mssql_pconnect
mssql_query
mssql_result
mssql_rows_affected
mssql_select_db

mssql_free_statement

Free statement memory (PHP 4 >= 4.3.2, PHP 5, PECL odbtp:1.1.1-1.1.4) bool mssql_free_statement ( resource stmt )

Code Examples / Notes » mssql_free_statement

Change Language

Free statement memory (PHP 4 >= 4.3.2, PHP 5, PECL odbtp:1.1.1-1.1.4)
bool mssql_free_statement ( resource stmt )