I owe you guys an apology. Will's question about MyIsam threw me off at first. That and Locomotive.
I just realized that when we cut the tutorial into Part 1 and Part 2 we should have put a note telling the reader that, in fact, the recipe creation will not work at that point. It will fail for exactly the reason you're seeing. We told MySQL that there would be a foreign key. We haven't told Rails about it though. And we can't create a recipe until we do. That comes next. Sorry guys. You're going to have to wait for the second installment. Or...
If you just can't wait to enter a recipe, just take the foreign key constraint (and the field) out of the script.
Again, my apologies. The tutorial was written and reviewed as one (long) work. When we chopped it into two pieces for publication, we obviously didn't cut cleanly. Lesson learned.
Best regards and best wishes for a safe and happy holiday,
Bill
Showing messages 1 through 2 of 2.
is the code complete ?
2007-01-06 23:59:31
nelsmartens
[View]
After too many discussions of metaprogramming, migration and 'what happens under the hood', I wondered if I would find a document that produced a functioning demo.
Your article made my week. Errors and all :)
Thank you,
Nels
is the code complete ?
2006-12-20 16:39:30
sbaptista
[View]
First of all, thanks for the quick response.
>It will fail for exactly the reason you're seeing...You're going to have to wait for the second installment.
OK, now I know I didn't miss something.
> If you just can't wait to enter a recipe, just take the foreign key constraint (and the field) out of the script.
Reminds me that I made a mental note to look into how Rails handles/supports database modifications (or maybe that would be a migration issue(?).
Any chance the next installment might speak to that?
Your article made my week. Errors and all :)
Thank you,
Nels