Mid-Atlantic Developer Conference - Call for Speakers



(PHP 5, PHP 7)

mysqli::store_result -- mysqli_store_resultTransfers a result set from the last query


Stil obiect-orientat

mysqli_result mysqli::store_result ([ int $option ] )

Stil procedural

mysqli_result mysqli_store_result ( mysqli $link [, int $option ] )

Transfers the result set from the last query on the database connection represented by the link parameter to be used with the mysqli_data_seek() function.



Numai stilul procedural: Un identificator al legăturii întors de mysqli_connect() sau mysqli_init()


The option that you want to set. It can be one of the following values:

Valid options
Name Description
MYSQLI_STORE_RESULT_COPY_DATA Copy results from the internal mysqlnd buffer into the PHP variables fetched. By default, mysqlnd will use a reference logic to avoid copying and duplicating results held in memory. For certain result sets, for example, result sets with many small rows, the copy approach can reduce the overall memory usage because PHP variables holding results may be released earlier (available with mysqlnd only, since PHP 5.6.0)

Valorile întoarse

Returns a buffered result object or FALSE if an error occurred.


mysqli_store_result() returns FALSE in case the query didn't return a result set (if the query was, for example an INSERT statement). This function also returns FALSE if the reading of the result set failed. You can check if you have got an error by checking if mysqli_error() doesn't return an empty string, if mysqli_errno() returns a non zero value, or if mysqli_field_count() returns a non zero value. Also possible reason for this function returning FALSE after successful call to mysqli_query() can be too large result set (memory for it cannot be allocated). If mysqli_field_count() returns a non-zero value, the statement should have produced a non-empty result set.



Although it is always good practice to free the memory used by the result of a query using the mysqli_free_result() function, when transferring large result sets using the mysqli_store_result() this becomes particularly important.


See mysqli_multi_query().

A se vedea și

add a note add a note

User Contributed Notes 4 notes

8 years ago
After reading through original notes and example above as well as wading through the documentation, I finally got a loop to work with two stored procedures.

Using the results of the first one as a parameter for the second one. Easier to do this way than a huge modified sequence of Inner Join queries.

Hope this helps others...

// Connect to server and database
$mysqli        = new mysqli("$dbServer", "$dbUser", "$dbPass", "$dbName");

// Open First Stored Procedure using MYSQLI_STORE_RESULT to retain for looping
$resultPicks = $mysqli->query("CALL $proc ($searchDate, $maxRSI, $incRSI, $minMACD, $minVol, $minTrades, $minClose, $maxClose)", MYSQLI_STORE_RESULT);

// process one row at a time from first SP
while($picksRow = $resultPicks->fetch_array(MYSQLI_ASSOC)) {
// Get Parameter for next SP
$symbol     = $picksRow['Symbol'];

// Free stored results

// Execute second SP using value from first as a parameter (MYSQLI_USE_RESULT and free result right away)
$resultData    = $mysqli->query("CALL prcGetLastMACDDatesBelowZero('$symbol', $searchDate)", MYSQLI_USE_RESULT);
$dataRow    = $resultData->fetch_array(MYSQLI_ASSOC);

// Dump result from both related queries
echo "<p>$symbol ... Num Dates: " . $dataRow['NumDates'];

// Free results from second SP


// Free results from first SP

// close connections

function clearStoredResults($mysqli_link){
$l_result = $mysqli_link->store_result()){
lau at goldenweb dot com dot au
10 years ago
Beware when using stored procedures:
If you connect to the database and then call dbproc A followed by a call to db proc B and then close the connection to the db, the second procedure call will not work.

It looks like there is a bug in MYSQL or mysqli that returns an extra recordset than you would expect. It then doesn't let you call another stored procedure until you finish processing all the recordsets from the first stored procedure call.

The solution is to simply loop through the additional recordsets between calls to db procs. Here is a function that I call between db proc calls:

function ClearRecordsets($p_Result){
$l_result = $this->Mysqli->store_result()){

8 years ago
It also seems, that executing a SET statement in multi_query() returns an extra recordset too, which one would not expect.
Tex Morgan
4 years ago
There's a simpler way to clear out database stored procedure problems:

class MySQLiQuery {
     protected $_resultSet;
     protected $databaseConnection;

    protected function free(){

    protected function checkMoreResults(){
            return true;
        } else {
            return false;

    protected function clearResults(){
                $this->clearResults(); // <----------- recursive call is your friend
To Top