At this point, you have most of the ingredients needed to create simple web
applications in Rails, provided you’re willing to stick to a single
database table. There’s one large problem remaining: users (and programs
connecting through web services) don’t always put in the data you want them to put
in. Making your application work reliably requires checking information as
it comes in and interacting with users so that they know how to get it
right.
As you’ll see throughout this chapter, Rails expects all data
validation to happen in the model layer and provides tools that make it
easy to do there. If you find yourself putting data-checking code into
the views or the controllers, pause for a moment—you’re quite likely
doing something wrong.
The one probable exception is if you’re adding warnings for users
working in your forms, avoiding a round trip to the server, but you
should never rely on those to limit your data to the correct types. All
that work should do is give users more information more rapidly.
You are currently reading a PREVIEW of this book.
Get instant access to over
$1 million worth of books and videos.