SQLSTATE[HY000]: General error: 1615

diakourtis

https://laracasts.com/discuss/channels/laravel/general-error-1615-prepared-statement-needs-to-be-re-prepared-selecting-mysql-view
show on computer
// run the SQL against the PDO connection. Then we can calculate the time it
// took to execute and log the query SQL, bindings and time in our memory.
try {
$result = $callback($query, $bindings);
}

    // If an exception occurs when attempting to run a query, we'll format the error
    // message to include the bindings with SQL, which will make this exception a
    // lot more helpful to the developer instead of just the database's errors.
    catch (Exception $e) {
        throw new QueryException(
            $query, $this->prepareBindings($bindings), $e
        );
    }
 
    return $result;
}

Hello, I receive this error every day at about 6:30. Anybody knows how to fix this error? I found some answers at
https://laracasts.com/discuss/channels/laravel/general-error-1615-prepared-statement-needs-to-be-re-prepared-selecting-mysql-view

diakourtis

“SQLSTATE[HY000]: General error: 1615 Prepared statement needs to be re-prepared (SQL: select * from ti_pages where status = 1 and permalink_slug = limit ▶”

diakourtis

I investigated the issue and found out
It appears that the following file is constantly checking pages for updates and is generating unique URL Slugs for them:
vendor/tastyigniter/flame/src/Database/PermalinkMaker.php
The file in question is the one that executes the following MySQL Query:
SQL: select * from ti_pages where status = 1 and permalink_slug = reservation limit 1
However, once this MySQL Query is executed the table “ti_pages” is marked as crashed by the MySQL Service on the server, thus the reason why you are being displayed with the following error message:
SQLSTATE[HY000]: General error: 1615 Prepared statement needs to be re-prepared (HY000)
The exact meaning of the error message is that the SQL Query creates a new MySQL Statement in the Database with ID 1615, which for some reason becomes corrupted and crashes the “ti_pages” table.
Anybody else run on this issue and anybody found a workaround?
Thank you!