Within about two weeks of getting
it, Kevin had removed every single screw, bolt, and nut he could. He explored all the circuits
and wires. But best of all, he somehow managed to successfully rebuild it using almost all of the
parts he had taken out (there were a few leftover screws and parts that it clearly didn??™t need).
Looking back, Kevin was always doing stuff like that. Regardless of the cost or the consequences,
he just has to know how things work. We??™re guessing that, as a fellow programmer,
you do, too. So while it??™s not really a requirement to developing great Active Record programs,
knowing just where the Active Record source code is and how it really works is something we
think we should spend a little time on. This way you can rip the guts out and take a look whenever
you want??”just remember to put it all back together before your mom gets home!
187
C H A P T E R 8
?– ?– ?–
Finding the Code
At the start of this book, we mentioned that Active Record is really nothing more than Ruby code.
This turns out to be a great fact for those of us who want to dive into the source code, because all
we need to know is where the files are and, of course, how to follow a Ruby program.
Pages:
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427