You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per code documentation (and as per the percieved intention to move towards use of Exceptions and their handling) the database class is supposed to throw Exceptions for certain issues.
But since the related constants are not being set, MySQLi still just uses boolean false return values.
This is problematic, as it provides no good feedback when a prepared statement is not properly formatted (e.g. placeholder in the wrong location as in #1125)
Current Behavior
Exception is thrown on functional issues, but not on MySQLi specific validations / behaviour
Possible Solution
Set at least MYSQLI_REPORT_ERROR, potentially also MYSQLI_REPORT_STRICT if that does not break too much at once.
Steps to Reproduce (for bugs)
Build a wrong prepared statement, notice white screen, see strange error that call to execute() was attempted on a boolean
The text was updated successfully, but these errors were encountered:
Expected Behavior
As per code documentation (and as per the percieved intention to move towards use of Exceptions and their handling) the database class is supposed to throw Exceptions for certain issues.
But since the related constants are not being set,
MySQLi
still just uses booleanfalse
return values.This is problematic, as it provides no good feedback when a prepared statement is not properly formatted (e.g. placeholder in the wrong location as in #1125)
Current Behavior
Exception is thrown on functional issues, but not on MySQLi specific validations / behaviour
Possible Solution
Set at least
MYSQLI_REPORT_ERROR
, potentially alsoMYSQLI_REPORT_STRICT
if that does not break too much at once.Steps to Reproduce (for bugs)
Build a wrong prepared statement, notice white screen, see strange error that call to
execute()
was attempted on a booleanThe text was updated successfully, but these errors were encountered: