On Sep 6, 1:48 pm, RajeshD <[EMAIL PROTECTED]> wrote: > > It seems like the Choice table is easier on the user. You tell them > > to go to the Choices table to enter all the look-up data, as opposed > > to giving them X tables to wade through. > > As you said, it is probably a DB design question -- even within a > single project, you might need to use both approaches. > > My $.02: > > If you need special validation based on the type of the lookup data, > the separate tables option works better. You can still make them go to > one screen to manage all the lookup data (you're just going to have to > build that screen yourself ;) > > Also, if you want foreign key relations to the choice data, separate > tables might work better. > > I would personally never mix person name prefix data with a list of > states in the same table even if you have a "type" field to qualify > such data. To me, that kind of user convenience is not worth the loss > in data integrity because one can always unify those lookups in a user- > friendly UI.
Thanks. That all makes sense. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
