I started with rails a few weeks ago and I’ve been very impressed with
the whole framework. My first project after the cookbook was a small
application connecting to Postgres. This was originally a port of an
Access application so I was delighted with the new facilities for
constraint checks, triggers, etc.
As I started to write the front-end though I noticed myself rewriting
the same checks in my models so that rails can validate data before it
hits the database. Otherwise the database throws an error instead of
rails having that nice ‘errors’ hash. I began to contemplate models that
use before_save and similar methods (instead of triggers) to log
So to test things out I’m refactoring again using an sqlite database
(just to keep it simple for now) and keeping all of the code in rails.
I use a migration to setup and populate the tables, and then put all my
checks in the models.
Sofar it’s working swimmingly (it’s a very small app), but I was
wondering what the pro’s/con’s of this setup are.
Performance isn’t an issue with my current project, but for the future
what can I expect? My first crack at the problem involved checking data
twice anyway so this isn’t any slower but maybe I’m going about this the
wrong way? More importantly, what about data integrity?