> So I'm suggesting that we should have a feature for models to RESCUE > (catch) the exception raised by the database connection and turn it > into a nice error message, like what validations do.
This kind of solution is too brittle and IMO can never work well. Database errors are (at least in most cases) not spec'ed, or even documented, and might differ between different versions of databases. sharon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
