If you have another person who feels more
comfortable in the database realm or you have other reasons that require you do more in the
database realm, it probably makes sense to give up some of the clean and simple Active Record
features.
Is There an Easier or More Efficient Way?
Active Record was created to make working with databases simple for Ruby developers. Over
time, it??™s evolved into a pretty complete realm allowing those of us who prefer to keep as much
as possible in code to actually stick to our world almost 100 percent of the time. We can do just
about everything from defining and setting up our schema with Active Record migrations, to
populating massive amounts of data with fixtures, to incorporating complex business logic
through data validations and callbacks, and we can even move from one database backend to
another with very little effort. And we can do almost all of this without even having to know all
that much about the SQL! This means we can spend more time focusing on our business logic
and on becoming better Ruby programmers as a whole.
Pages:
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372