Error handling in application

[cali_dotcom]

hi guys, i am currently building a nice website and i was just wondering about the best way to handle errors, database and webservices errors.
i was thinking on implementing a mixture of file and db logging. so basically i would log to db all the time and then i would log to filewhen there is a db error. i am also thinking of the best way to handle this.
the site is built in Zend Framework, so i am considering using the zend error handling and logging functionality, but i worried it might be too much overhead.

do you guys have any suggestions as to the best way to go about this? zend, pear or any other?

[Bunkermaster]

It depends what you want to do with the logs. If you (realistically) will never use them, just use the least resource consuming.
If, like me, paranoia drives your life and you want/need to know what everyone did everywhere, I suggest you draft a list of data you want accessible and features you want to access that data through (sorting, filters, computing, etc). Then you compare what you want with what each solution offers.
You might also want to log offsite on a one way only interface so you can access the history of what happened even if some dude crashed it for some lulz.

Depends what you want/need to do really.