{"id":23422,"date":"2022-11-25T22:49:42","date_gmt":"2022-11-25T17:19:42","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-what-to-do-with-mysqli-problems-errors-like-mysqli_fetch_array-argument-1-must-be-of-type-mysqli_result-and-such\/"},"modified":"2022-11-25T22:49:42","modified_gmt":"2022-11-25T17:19:42","slug":"solved-what-to-do-with-mysqli-problems-errors-like-mysqli_fetch_array-argument-1-must-be-of-type-mysqli_result-and-such","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-what-to-do-with-mysqli-problems-errors-like-mysqli_fetch_array-argument-1-must-be-of-type-mysqli_result-and-such\/","title":{"rendered":"[Solved] What to do with mysqli problems? Errors like mysqli_fetch_array(): Argument #1 must be of type mysqli_result and such"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

TL;DR<\/h3>\n
    \n
  1. Always have mysqli_report(MYSQLI_REPORT_ERROR | MYSQLI_REPORT_STRICT);<\/code> in your mysqli connection code and always check the PHP errors<\/em>.<\/li>\n
  2. Always replace every PHP variable in the SQL query with a question mark, and execute the query using prepared statement<\/strong><\/a>. It will help to avoid syntax errors of all sorts.<\/li>\n<\/ol>\n

    Explanation<\/h3>\n

    Sometimes your MySQLi code produces an error like mysqli_fetch_assoc() expects parameter 1 to be mysqli_result, boolean given...<\/code>, Call to a member function bind_param()...<\/code> or similar. Or even without any error, but the query doesn’t work all the same. It means that your query failed to execute.<\/p>\n

    Every time a query fails, MySQL has an error message that explains the reason<\/strong>. In the older PHP versions such errors weren’t transferred to PHP, and all you’d get is a cryptic error message mentioned above. Hence it is very important to configure PHP and MySQLi to report MySQL errors to you. And once you get the error message, fixing it will be a piece of cake.<\/p>\n

    How to get the error message in MySQLi<\/h3>\n

    First of all, always have this line before MySQLi connect in all<\/strong> your environments:<\/p>\n

    mysqli_report(MYSQLI_REPORT_ERROR | MYSQLI_REPORT_STRICT);\n<\/code><\/pre>\n
    After that, all MySQL errors will be transferred into PHP exceptions. An uncaught exception, in turn, makes a PHP fatal error. Thus, in case of a MySQL error, you’ll get a conventional PHP error. That will instantly make you aware of the error cause. And the stack trace will lead you to the exact spot where the error occurred.<\/p>\n
    How to get the error message from PHP<\/h3>\n
    Here is a gist of my article on PHP error reporting<\/a>:
    \nReporting errors on a development and live servers must be different. On the development server it is convenient to have errors shown on-screen, but on a live server error messages must be logged instead, so you could find them in the error log later.<\/p>\n
    Therefore, you must set corresponding configuration options to the following values:<\/p>\n