Thank you so much for your reply Colin. I believe you are spot on with your answer and what you suggest will work and is the correct solution.
For sake of my sanity though, is this solution more of a Rails convention or have I been getting standard database design confused in my head for a number of years? To my previous understanding I still see it as one vehicle has one vehicle_type. Almost like vehicle_type is a child table to the parent vehicle. Is this wrong thinking for all database design or just Rails conventions? -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
