Fatal error Call to a member function bind param on boolean

Question

I m busy on a function that gets settings from a DB  and suddenly  I ran into this error   Fatal error  Call to a member function bind param   on boolean in C  xampp2 htdocs application classes class functions php on line 16   Normally  this would mean that I m selecting stuff from unexisting tables and stuff  But in this case  I  m not     Here s the getSetting function   public function getSetting  setting         query    this- gt db- gt conn- gt prepare  SELECT value  param FROM ws settings WHERE name             query- gt bind param  s    setting        query- gt execute         query- gt bind result  value   param        query- gt store result        if   query- gt num rows    gt  0                while   query- gt fetch                           return  value              if   param      1                                  this- gt tpl- gt createParameter  setting   value                                     else                   invalid setting request    setting             The  this- gt db variable is passed through a constructor  In case of need  here is it   public function   construct  db   data   tpl         this- gt db    db       this- gt tpl    tpl       this- gt data    data       this- gt data- gt setData  global    theme    this- gt getSetting  theme         Also  since I m making use of a database  my database connection   class Database       private  data       public function   construct  data             this- gt data    data       this- gt conn   new MySQLi         this- gt data- gt getData  database    hostname            this- gt data- gt getData  database    username            this- gt data- gt getData  database    password            this- gt data- gt getData  database    database              if   this- gt conn- gt errno                    failed db connection    this- gt conn- gt errno             date default timezone set  Europe Amsterdam        I ve already tested the connection  100  positive that it works as intended  I m setting the DB connection things in a configuration file    database    gt  array       hostname    gt   127 0 0 1        username    gt   root        password    gt               database    gt   wscript      Now the weird thing is  the table exists  the requested setting exists  the DB exists  but still  that error won t leave  Here s some proof that the DB is correct

User · Answer

Following two are the most probable cause of this issue    Spelling mistake either in column names or table name Previously established statement is not closed  Just close it before making the prepared statement       stmt- gt close        lt  lt  lt -----This fixed the issue for me   stmt    conn- gt prepare  Insert statement

User · Answer

In my experience the bind param was fine but I had mistaken the database name so  I changed only the database name in the connection parameter and it worked perfectly  I had defined root path to indicate the root folder  include path to include folder and base url for the home url of website  This will be used for calling them anywhere they are required

User · Answer

This particular error has very little to do with the actual error  Here is my similar experience and the solution     I had a table that I use in my statement with  database-name  login composite name  I thought this wouldn t be a problem  It was the problem indeed  Enclosing it inside square brackets solved my problem    database-name    login    So  the problem is MySQL preserved words  other way around     make sure your columns too are not failing to this type of error scenario

User · Answer

Sometimes  it is also because of a wrong table name or column name in the prepare statement   See this

User · Answer

I noticed that the error was caused by me passing table field names as variables i e  I sent    stmt    this- gt con- gt prepare  INSERT INTO tester   test1   test2  VALUES            instead of    stmt    this- gt con- gt prepare  INSERT INTO tester  test1  test2  VALUES            Please note the table field names contained   before field names  They should not be there such that  field1 should be field1

User · Answer

Another situation that can cause this problem is incorrect casting in your queries   I know it may sound obvious  but I have run into this by using tablename instead of Tablename  Check your queries  and make sure that you re using the same case as the actual names of the columns in your table

User · Answer

The problem lies in    query    this- gt db- gt conn- gt prepare  SELECT value  param FROM ws settings WHERE name         query- gt bind param  s    setting     The prepare   method can return false and you should check for that  As for why it returns false  perhaps the table name or column names  in SELECT or WHERE clause  are not correct   Also  consider use of something like  this- gt db- gt conn- gt error list to examine errors that occurred parsing the SQL   I ll occasionally echo the actual SQL statement strings and paste into phpMyAdmin to test  too  but there s definitely something failing there

User · Answer

Sometimes explicitly stating your table column names  especially in an insert query  may help  For example   the query   INSERT INTO tableName param1  param2  param3  VALUES            may work better as opposed to   INSERT INTO tableName VALUES

User · Answer

Any time you get the         Fatal error  Call to a member function bind param   on boolean       it is likely because there is an issue with your query  The prepare   might return FALSE  a Boolean   but this generic failure message doesn t leave you much in the way of clues  How do you find out what is wrong with your query  You ask   First of all  make sure error reporting is turned on and visible  add these two lines to the top of your file s  right after your opening  lt  php tag   error reporting E ALL   ini set  display errors   1     If your error reporting has been set in the php ini you won t have to worry about this  Just make sure you handle errors gracefully and never reveal the true cause of any issues to your users  Revealing the true cause to the public can be a gold engraved invitation for those wanting to harm your sites and servers  If you do not want to send errors to the browser you can always monitor your web server error logs  Log locations will vary from server to server e g   on Ubuntu the error log is typically located at  var log apache2 error log  If you re examining error logs in a Linux environment you can use tail -f  path to log in a console window to see errors as they occur in real-time    or as you make them   Once you re squared away on standard error reporting adding error checking on your database connection and queries will give you much more detail about the problems going on  Have a look at this example where the column name is incorrect  First  the code which returns the generic fatal error message    sql    SELECT  foo  FROM  weird words  WHERE  definition         query    mysqli- gt prepare  sql       assuming  mysqli is the connection  query- gt bind param  s    definition    query- gt execute      The error is generic and not very helpful to you in solving what is going on   With a couple of more lines of code you can get very detailed information which you can use to solve the issue immediately  Check the prepare   statement for truthiness and if it is good you can proceed on to binding and executing    sql    SELECT  foo  FROM  weird words  WHERE  definition        if  query    mysqli- gt prepare  sql        assuming  mysqli is the connection      query- gt bind param  s    definition        query- gt execute           any additional code you need would go here    else        error    mysqli- gt errno          mysqli- gt error      echo  error     1054 Unknown column  foo  in  field list      If something is wrong you can spit out an error message which takes you directly to the issue  In this case there is no foo column in the table  solving the problem is trivial   If you choose  you can include this checking in a function or class and extend it by handling the errors gracefully as mentioned previously

User · Answer

You should always try as much as possible to always put your statements in a try catch block     it will always help in situations like this and will let you know whats wrong  Perhaps the table name or column name is wrong

User · Answer

Even when the query syntax is correct  prepare could return false  if there was a previous statement and it wasn t closed  Always close your previous statement with   statement- gt close      If the syntax is correct  the following query will run well too

User · Answer

prepare return a boolean only when it fails therefore FALSE  to avoid the error you need to check if it is True first before executing    sql    SELECT value  param FROM ws settings WHERE name       if  query    this- gt db- gt conn- gt prepare  sql         query- gt bind param  s    setting        query- gt execute          rest of code here  else       error    don t go further    var dump  this- gt db- gt error

[php] Fatal error: Call to a member function bind_param() on boolean

Examples related to php

Examples related to mysql

Examples related to mysqli