I wish validations were tightly integrated into the database. Validations are something that ActiveRecord was not good at.
For example, validating uniqueness or presence of an associated object would actually not enforce validation (under rare race conditions). This is because it is impossible for Ruby to do constraints for databases. The proper way to validate would be to add constraints into the database itself. Thus, I propose that we have a constraint-error-parsing validation system. All validations would be defined in the migrations as constraints, and the validation system would check for error messages AFTER the database call. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
