Full Text Search

[hasek522]

I am trying to use a FULLTEXT sql search but am encountering a sql error I cant figure out.

Here is the error:

 

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /nfs/c03/h01/mnt/48237/domains/hairneedhelp.net/html/search.php on line 15

 

Here is the code:

 

$search = $_POST['search'];

$search = '%' . $search . '%';

$db = mysql_connect($dbhost, $dbuser, $dbpassword);

mysql_select_db($dbdatabase, $db);

$search = mysql_real_escape_string($search);

$sql = "SELECT * FROM stylists WHERE MATCH(firstname, lastname, city, salon, specialty) AGAINST ('" . $search . "');";

$query = mysql_query($sql);

while($row = mysql_fetch_array($query))

[DarkWater]

You always need to do debugging and error checking on your queries in the development stage.  Change:

$query = mysql_query($sql);

To:

$query = mysql_query($sql) or die(mysql_error());

[Jabop]

I would still include or die() in a production environment also

[DarkWater]

There are better ways to handle it at that level if you're making a serious application.  If it's just a little PHP thing, then sure, you can keep the die clause in there.

[Jabop]

Example of a better method?

[DarkWater]

You would probably have exceptions set up for queries.

[discomatt]

Example of a better method?

 

A proper error handling class. die()'ing is horrible. I'd rather purge all object buffers and output a decent looking error page, then die() silently.

 

This allows you to hide details ( revealing potential database structure, ect ) in a production environment with a debug constant set to false, and allows you to see them while programming, or, debugging.

[DarkWater]

Precisely.  die() is just plain ugly for production environments.