PHP 8.1.31 Released!

    mysqli::store_result

    mysqli_store_result

    (PHP 5, PHP 7, PHP 8)

    mysqli::store_result -- mysqli_store_result — Transfers a result set from the last query

    Description

    Object-oriented style

    public mysqli::store_result(int $mode = 0): mysqli_result|false

    Procedural style

    mysqli_store_result(mysqli $mysql, int $mode = 0): mysqli_result|false

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

    Parameters

    mysql

    Procedural style only: A mysqli object returned by mysqli_connect() or mysqli_init()

    mode

    The option that you want to set. As of PHP 8.1, this parameter has no effect. 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)

    Return Values

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

    Note:

    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.

    Errors/Exceptions

    If mysqli error reporting is enabled (MYSQLI_REPORT_ERROR) and the requested operation fails, a warning is generated. If, in addition, the mode is set to MYSQLI_REPORT_STRICT, a mysqli_sql_exception is thrown instead.

    Changelog

    Version Description
    8.4.0 Passing the mode parameter is now deprecated. The parameter has had no effect as of PHP 8.1.0.

    Examples

    See mysqli_multi_query().

    Notes

    Note:

    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 Also

    Improve This Page

    Learn How To Improve This Page • Submit a Pull Request • Report a Bug
    ＋add a note

    User Contributed Notes 4 notes

    up
    11
    mitchind
    14 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...

    <?php
    // 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
    clearStoredResults($mysqli);

    // 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
    $resultData->free();

    }

    // Free results from first SP
    $resultPicks->free();

    // close connections
    $mysqli->close();

    #------------------------------------------
    function clearStoredResults($mysqli_link){
    #------------------------------------------
    while($mysqli_link->next_result()){
    if(    $l_result = $mysqli_link->store_result()){
    $l_result->free();
    }
    }
    }
    ?>
    up
    2
    filippo at ecoms dot it
    6 years ago
    Code to handling errors:

    if ($mysqli->multi_query($query)) {
    $result = $mysqli->store_result();
    if ($mysqli->errno == 0) {

    /* First result set or FALSE (if the query didn't return a result set) is stored in $result */

    while ($mysqli->more_results()) {
    if ($mysqli->next_result()) {
    $result = $mysqli->store_result();
    if ($mysqli->errno == 0) {
    /* The result set or FALSE (see above) is stored in $result */
    }
    else {
    /* Result set read error */
    break;
    }
    }
    else {
    /* Error in the query */
    }
    }
    }
    else {
    /* First result set read error */
    }
    }
    else {
    /* Error in the first query */
    }
    up
    -3
    Warner
    15 years ago
    It also seems, that executing a SET statement in multi_query() returns an extra recordset too, which one would not expect.
    up
    -5
    lau at goldenweb dot com dot au
    17 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:

    <?php
    #--------------------------------
    function ClearRecordsets($p_Result){
    #--------------------------------
    $p_Result->free();
    while(    $this->Mysqli->next_result()){
    if(    $l_result = $this->Mysqli->store_result()){
    $l_result->free();
    }
    }
    }

    ?>
    ＋add a note
    To Top