This method tells the server that it can dispose of the information it
holds about the current prepared statement.
This method can be called during a GC collection. Allocations should be
avoided if possible as it could crash the GC.
Notes:
In actuality, the server might not immediately be told to release the
statement (although this instance of Prepared will still behave as though
it's been released, regardless).
This is because there could be a ResultRange with results still pending
for retreival, and the protocol doesn't allow sending commands (such as
"release a prepared statement") to the server while data is pending.
Therefore, this function may instead queue the statement to be released
when it is safe to do so: Either the next time a result set is purged or
the next time a command (such as query or exec) is performed (because
such commands automatically purge any pending results).
Release a prepared statement.
This method tells the server that it can dispose of the information it holds about the current prepared statement.
This method can be called during a GC collection. Allocations should be avoided if possible as it could crash the GC.
Notes:
In actuality, the server might not immediately be told to release the statement (although this instance of Prepared will still behave as though it's been released, regardless).
This is because there could be a ResultRange with results still pending for retreival, and the protocol doesn't allow sending commands (such as "release a prepared statement") to the server while data is pending. Therefore, this function may instead queue the statement to be released when it is safe to do so: Either the next time a result set is purged or the next time a command (such as query or exec) is performed (because such commands automatically purge any pending results).