Not really following you here. The default layout of django auth is that you can have 100 people of the same name in multiple entries unaware that there is another person with the same name unless they try to make a username the same. Django, and most high level frameworks work so they increment database values automatically at every entry. So unless you explicitly define something, like a name, as unique it won't make a difference. That pesky instance field that you refer to comes free with Django.
Have you looked at the way auth does this? If so explain what you are trying to say in terms of auth please. It would be better to understand. On Sun, Apr 6, 2008 at 1:08 AM, LRP <[EMAIL PROTECTED]> wrote: > > This pesky problem transcends Django. But many Django users will > encounter it. > > Say we're creating a contact or registration application. > > What is the best way to deal with the problem of two or more people > with exactly the same name? > > This problem actually has two faces: > > 1) In an admin situation, it may be possible, though a bit pesky, to > add an Instance field; e.g. Prefix FirstName MiddleName LastName > Suffix Instance -- thus Mr. John Jasper Smith II 1; Mr. John Jasper > Smith II 2 would be two different records in the database. > > -- Is there a better way to deal with this? > > 2) In a public registration system, we may not want a registrant to > know that another John Jasper Smith II exists in the database. > > -- Is there a clever way to deal with this? > > Many thanks, > > Lloyd > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
