TYPO 2010-02-07T23:48:48-08:00 kacey the html code in _cart_item.html.erb doesn't work as written, there seems to be an open <tr> with no ending </tr>, and I cannot work out where to place the </tr>. 42272 128 111 218.186.9.249 128 1145 TYPO 2010-02-08T17:16:08-08:00 kacey Please remove previous erratum <tr>, typo with javascript defaults was causing the error. 42282 128 111 218.186.9.249 128 1145 SUGGEST 2010-01-22T12:30:27-08:00 Steven Harms I realize that the Store application is designed to give someone unfamiliar with Rails a really quick tour of what an awesome app you can make in a short time. Nevertheless, I feel like the discussion on the foreign key sqlite3 "hack" is a bit....hand-wavey? I don't know a lot about sqlite3 or SQL in general, but it feels like the book skips over this pretty quickly. When learning from a book i think "Hm, would i have thought to do that? Maybe with some Google-fu?" as a measure of "Did you _really_ get it." I don't think I would have come to putting these DDL calls in unless I had seen it in the book. Maybe explain what's going on here? Or put it in a footnote? Or a Joe Asks? Or cover the theory in one of the later chapters about DB design? 42139 143 111 72.163.0.129 143 1145 SUGGEST 2010-02-08T02:33:58-08:00 Steven Harms In the discussion of how to build a callback class and express it throughout all models, I think that a critical question is not addressed: (1) how do we get this file "sourced" into the Rails runtime. If you put it in lib as a module does it automatically get loaded up? How can we get it to run as the environment boots up. The example source file is given as a stand-alone script. (2) It appears that we're being encouraged to monkey-patch ActiveRecord::Base. While the ability to do this is one of the amazing joys of Ruby, it might be good to explain why this may or may not be a good idea. Many a tweet has gone out on the difficulty monkeypatching has introduced in code-sharing / debugging. 42273 412 111 24.130.173.204 412 1168