On Mon, Jan 3, 2011 at 12:18 AM, Colin Law <[email protected]> wrote:
>> However, I don't see why you'd use the second approach. It's more >> complex for no particular gain. > > The one time you might want to keep addresses, for example, in a > separate table, would be if your app had the concept of multiple users > at the same address. ?! `User has_many addresses` is a pretty standard scenario: work and home, billing vs. shipping, and so on, in which case of course it makes sense to have a separate "address" table. Even with the concept of *one* (home) address per user, I've had a use case that included tracking length of residence, so again, that's definitely a separate table. Any such design question requires context... FWIW, -- Hassan Schroeder ------------------------ [email protected] twitter: @hassan -- 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 this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
