4 replies to this topic

[bbqroast]

Well its me again!
I am writing some fancy code and I decided that the MySQL (can't jump to...) error was not what I wanted my users to see when they got the wrong page ID. So i changed the code to:

$body = mysql_result($data,0,"Body") or die("Page not found!");

Sadly however it still returns:

Warning: mysql_result() [function.mysql-result]: Unable to jump to row 0 on MySQL result index 5 in C:\web-server\thehub\framed.php on line 11

Page not found!

Well at least i managed to get the Page not found! part in, so anyone know how to remove the MySQL generated part??

[Alexander]

You will notice this is a warning, in fact E_WARNING in the engine. You can leave errors on and turn warnings off with the following line of code, provided you have placed this at the top of your code and have allowed changing of settings in run time.

For example:

error_reporting(E_ALL & ~E_WARNING);

You will notice this uses bitwise manipulation operators, so you can easily add your own options or constraints.

[__ak]

@Alexander

Just out of curiosity; what is the difference between your code and this?

error_reporting(E_ALL^E_WARNING);

[Alexander]

For this specific task they will produce the same result.

Why I do not suggest using your mentioned method; If you apply an exclusive OR to E_ALL and E_STRICT (which is set to OFF in E_ALL) it will enable it, which you presumably did not intend. A very simple example:

0001011111111111 ( E_ALL )
0000100000000000 ( E_STRICT )
0001111111111111 ( E_ALL ^ E_STRICT )
0001011111111111 ( E_ALL & ~E_STRICT )

[__ak]

Thanks alot!
Makes great sense.