On Mon, Mar 16, 2009 at 11:36 AM, Trey <jameslon...@gmail.com> wrote: > > Hello everyone, I am hoping someone has some experience in this > already. I have a rough idea of how to do it, but I am hoping to > discover a better way. > > What I have: > A contact manager. A contact has a set of data that makes sense on > anyone's version of a contact, things like name, email address, etc. > > Depending on the use of the contact manager, special fields may be > required. Something like, birthplace or SSN. > > I would like to build the contact manager for all purposes and have > those extra fields configured through the CRM's admin. > > My Plan: > What I have in mind is a standard columnar table that holds all the > basic fields. And then two additional tables, one for the customized > field names and one to related the custom fields to the contact. I can > foresee tons of performance issues and problems updating data. > > Does anyone have any advice, working example, snippet or other general > comment?
Your plan is fine, it's exactly what I would do in the same situation. With proper caching of the data, I wouldn't expect to see any serious performance issues with your plan. Assuming given adequate hardware. Sure it would be an issue if you have 100k users and are running this on a 5 year old laptop, but that isn't a good reason to not build the software properly. -- Frank Wiles Revolution Systems | http://www.revsys.com/ fr...@revsys.com | (800) 647-6298 --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
