Even though it is outside the scope, I'd say start simple and build slowly with related tables, those are easy to add to a system. I'd probably find the attributes you'd like to capture in the 'extra details' and start putting them in a table. Determine what the purpose of these attributes are, searching, reporting, calculations, etc and that should help you determine if you need more than one 'extra' table.
HTH John On Nov 29, 10:36 am, Ramdas S <ram...@gmail.com> wrote: > This is probably outside Django. But I am checking out since I am building > it with Django. > > I am building a specialized closed group social networking web site for > special set of medical practitioners. Idea for my client is to be a mini- > LinkedIn of sorts for this small community. > > We want to capture as many details as possible from some clinical practices, > to education, work experience, papers submitted etc. However at registration > time we want to limit it to just the basic details like name, email and may > be some license number. > > However over a period of time we would like the user to add details. > > Do I build one large UserProfile Table, with ForeignKey to colleges, > specializations etc or do I break it up into number of smaller profiles, and > link each profile to a User. What's the best practice? > > -- > Ramdas S -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
