Warning: mysqli::mysqli() [mysqli.mysqli]: (HY000/2003): Can't connect to MySQL server on 'mysql7.......' (111) in /home/....t/defaults/co.php on line 8
and
Warning: mysqli_query() [function.mysqli-query]: Couldn't fetch mysqli in /home/..../co.php on line 18

Anyway how i can prevent these errors from showing up my on my site? In my file (co.php), i have this:
I have tried these various codes:
and yet, none of them is currently able to make mysqli shut up when it cant connect

I have a custom error handler setup for my sites. When it is in development it will show the error in full, but when the site is live it displays a "gentle" message (or none at all if you wish), and instead it sends an email alerting me to the fact that an error occured.

Take a look at this thread: Exception Handling

There is a little bit more to it than what you can see there, but if this is the kind of thing you are looking for give me a nod and I will post the full code for you.

__________________
Hightower's Softpolio

I still dont understand it that much. If i remember correctly, php exceptions have do not work well with catching mysql errors

Thats because its not throwing an exception, its producing a warning.

This may be of some use to you: http://uk.php.net/set_error_handler

as an alternative, on the production you may want to run with :
That will stop any warnings etc from being displayed.

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

You can suppress errors, although it's not recommended, by adding an @ symbol in front of the function:


The better way is to, as Hightowers suggested, set up different modes of error displaying for different users. For yourself, the developer, you want to see these warnings, but users don't.

To not show warnings you can do:


Note to self: Type quicker next time so that sketchMedia doesn't beat me to it. Git!

__________________
The man who comes back through the Door in the Wall will never be quite the same as the man who went out.

A good point in your post:
Indeed its not recommended, having to grep through code to find those pesky things when your script is just quietly falling over is a tedious task at best!

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

Yeah, plus from what I hear it slows down your script.

Yes, i believe its because internally it converts this:

e.g.to this:

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)