This is my PHP sql statement and it’s returning false while var dumping
$password_md5 = md5($_GET['password']); $sql = $dbh->prepare('INSERT INTO users(full_name, e_mail, username, password, password_plain) VALUES (:fullname, :email, :username, :password, :password_plain)'); $result = $sql->execute(array( ':fullname' => $_GET['fullname'], ':email' => $_GET['email'], ':username' => $_GET['username'], ':password' => $password_md5, ':password_plain' => $_GET['password']));
Sometimes your PDO code produces an error like
Call to a member function execute() or similar. Or even without any error but the query doesn’t work all the same. It means that your query failed to execute.
Every time a query fails, MySQL has an error message that explains the reason. Unfortunately, by default such errors are not transferred to PHP, and all you have is a silence or a cryptic error message mentioned above. Hence it is very important to configure PHP and PDO to report you MySQL errors. And once you get the error message, it will be a no-brainer to fix the issue.
In order to get the detailed information about the problem, either put the following line in your code right after connect
$dbh->setAttribute( PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION );
$dbh is the name of your PDO instance variable) or – better – add this parameter as a connection option. After that all database errors will be translated into PDO exceptions which, if left alone, would act just as regular PHP errors.
There is a very small chance that in case of some specific error an exception won’t be thrown. If your
execute() call returns
false but there is no exception, check the
PDO::errorInfo() like this,
trigger_error("PDO errorInfo: ".$dbh->errorInfo());
After getting the error message, you have to read and comprehend it. It sounds too obvious, but learners often overlook the meaning of the error message. Yet most of time it explains the problem pretty straightforward:
- Say, if it says that a particular table doesn’t exist, you have to check spelling, typos, letter case. Also you have to make sure that your PHP script connects to a correct database
- Or, if it says there is an error in the SQL syntax, then you have to examine your SQL. And the problem spot is right before the query part cited in the error message.
You have to also trust the error message. If it says that number of tokens doesn’t match the number of bound variables then it is so. Same goes for absent tables or columns. Given the choice, whether it’s your own mistake or the error message is wrong, always stick to the former. Again it sounds condescending, but hundreds of questions on this very site prove this advice extremely useful.
Note that in order to see PDO errors, you have to be able to see PHP errors in general. To do so, you have to configure PHP depends on the site environment:
on a development server it is very handy to have errors right on the screen, for which displaying errors have to be turned on:
while on a live site, all errors have to be logged, but never shown to the client. For this, configure PHP this way:
error_reporting(E_ALL); ini_set('display_errors', 0); ini_set('log_errors', 1);
error_reporting should be set to
E_ALL all the time.
Also note that despite the common delusion, no try-catch have to be used for the error reporting. PHP will report you PDO errors already, and in a way better form. An uncaught exception is very good for development, yet if you want to show a customized error page, still don’t use try catch for this, but just set custom error handler. In a nutshell, you don’t have to treat PDO errors as something special but regard them as any other error in your code.
Sometimes there is no error but no results either. Then it means, there is no data to match your criteria. So you have to admit this fact, even if you can swear the data and the criteria are all right. They are not. You have to check them again. I’ve got an article that can help in this matter, How to debug database interaction with PDO. Just follow this instruction step by step and either have your problem solved or have an answerable question for Stack Overflow.