On Apr 6, 2:08 am, Michael <[EMAIL PROTECTED]> wrote: > 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. >
Ok, yes. It all comes clear. We have two ways of differentiating -- id value and username (which must be unique). Not thinking clearly this early in the a.m. 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 -~----------~----~----~----~------~----~------~--~---
