Now it might be that as an ex-DBA I find this a good idea, but anyway …
I think it bugs a lot of people that a Rails application doesn’t hep with database consistency and anyway that’s a tough (and database specific) issue.
But I recently found this gem (somewhat under utilised it seems, so maybe there is not much interest in this idea).
But this seems to be a great solution to providing database-agnostic constraint mechanism to ensure bad data does not end up in your database.
Would it be worthwhile to add such a feature to the next version of Rails?
Thanks for listening.