The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Another question i have is can i make it so the query is not case sensitive?

For example when i search "Welcome" i get a result but when i search "welcome" i get nothing.

Normally it should already be non case sensitive
You probably have a case-sensitive column types like BINARY, VARBINARY, or BLOB
so if you change these to CHAR, VARCHAR, or TEXT, the case-insensitive searches will also work

Normally it should already be non case sensitive
You probably have a case-sensitive column types like BINARY, VARBINARY, or BLOB
so if you change these to CHAR, VARCHAR, or TEXT, the case-insensitive searches will also work

The column type is LONGTEXT would that be case sensitive over just TEXT ?

Two points: you should never select * from a table, as you run the risk of the table changing in the future, and your code not being prepared to handle it.

Also: You should never concatenate variables directly into your SQL. You should Parameterize them (http://us.php.net/mysqli) in order to avoid anyone maliciously or unintentionally corrupting or deleting your database.

Two points: you should never select * from a table, as you run the risk of the table changing in the future, and your code not being prepared to handle it.

Also: You should never concatenate variables directly into your SQL. You should Parameterize them (http://us.php.net/mysqli) in order to avoid anyone maliciously or unintentionally corrupting or deleting your database.

I just had * for testing and will be changed.

Most of the variables are taken care of before used int he SQL but some are escaped with $db->sql_escape()