> Models are the gatekeepers to your database. So long as you are in an > environment where you fully control access to the underlying database, there > should be no need to add any database validations (although I know a few DB > administrators who choke on such ideas).
I don't think this is true even if you had full control over the database. in practice, there are some migrations that can't be written without hitting the database directly, thus bypassing some models. -- John Feminella Principal Consultant, BitsBuilder LI: http://www.linkedin.com/in/johnxf SO: http://stackoverflow.com/users/75170/ On Mon, Jul 4, 2011 at 19:24, Andrew Skegg <[email protected]> wrote: > Adrian Caceres <caceresad@...> writes: > >> >> Normally all my validation is done in my models. >> >> Michael Hart in his rails tutorial explains why the uniqueness >> validation should also be done at the database layer ( >> http://ruby.railstutorial.org/chapters/modeling-and-viewing-users- > one#sec:the_caveat). >> >> I am curious if people have experienced other validations that should >> also be done at the database layer? >> >> thanks >> > > Models are the gatekeepers to your database. So long as you are in an > environment where you fully control access to the underlying database, there > should be no need to add any database validations (although I know a few DB > administrators who choke on such ideas). > > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: 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/rubyonrails-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: 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/rubyonrails-talk?hl=en.
