Errors are, as you say, database-specific. However, we already do have database specific code, so it won't be causing any portability issues that were not there in the first place.
That said, perhaps the simplest way of getting this started is to implement the database_validates_constraint method and have everything else work off of that. This seems like a good overall abstraction layer to work on top of, unless the database also sends back an integer error code. If the database layer does send back an integer error code, then we could also support an :error_code option. database_validates_length_of, database_validates_presence_of, and database_validates_reference_to can be implemented by the database_validates_constraint. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
