On 29 March 2010 11:23, Paritian Thakkar <[email protected]> wrote: > Colin Law wrote: > >> Yes, why complicate matters. >> >> Have you considered that a user might be both a customer and an >> employee? Your model would preclude that I think. Are you sure it >> would not be better just to have the user model who can be either or >> both just by attribute contents? >> >> Colin > > Valid point :) > > I do not want to combine Customer and Employee tables because they have > quite different attributes... > > Employee has department, manager, roles etc... > Customer has current status, credit card info etc.. bunch of stuff I > will collect on registration.. If I combine them, the resulting table > will be a little too huge..
Assuming you plan to use STI for the tables then the table contains all the attributes for both anyway. Presumably most of the stuff is varchar which are variable length fields. so consume very little space. How many million customers are you expecting so that db size becomes a factor? :) Colin -- 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.
