Re: Internal server error - table too big?

[Phillip Ward]

Quote

I'm not checking for errors after every call, but I do after the mysql_connect. Where would be the best place to send the errors and how would I do this?

Anywhere and everywhere that your application goes to the database has the potential to fail. Check for errors after every single one.

Quote

I'm not checking for errors after every call, but I do after the mysql_connect. Where would be the best place to send the errors and how would I do this?

Where you log the errors is up to you; personally, I prefer an old-fashioned text file that you write to sequentially (open file, write timestamp and message, close file). Add an extra page into your application that allows you to (a) view the log [remotely] and (b) delete the log file, so it doesn't fill up your server, over time.

Regards, Phill W.