Variations on a table for different clients?
Does anyone have any experience with working with systems where different clients all need variations on the same basic table; there might be, say, 10 common fields, but each client will need an additional 2 or 3 that are specific to them (and, possibly, not need 1 or 2 of the common ones).
What approaches or practices will help streamline work and prevent such variations from becoming a headache to maintain? (And yes, its likely to be more than one table that will require these variations).
-- Thanks
Derek
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home