[eluser]Jay Callicott[/eluser]
What irritates me ab CI (and I love CI I have 20+ apps running off a shared CI framework installation in production) - is that I don't see a way to gracefully handle DB errors, and in php programming most of the errors that can stop down apps are of course DB errors.
Most of us know about PEAR DB and MDB2 where you can run a query and say if PEAR:

B_Error($res) blah blah and you have a chance to log the SQL and or handle the error gracefully.
With CI if you have debugging on it shows a big DB error page with the error. I want a better way to handle DB errors. Trying a try/catch doesn't seem to work.
Anybody have ideas? It seems like the documention assumes you will never have any db errors and that's irritating. I wish I could run a query and have something like $this->db->db_error() or something where I could then handle the db error. Thoughts??