Since all my looks up are by id and I am not using admin, I should be ok. I was not sure if django auth framework used it internally anywhere.
On Jan 19, 6:03 am, Karen Tracey <[email protected]> wrote: > On Tue, Jan 19, 2010 at 3:17 AM, zweb <[email protected]> wrote: > > > I am planning to drop unique key constraint on "name" column of > > auth_group table. > > > Any possible issues it may cause? > > Yes. With the unique constraint in place, .get() by name is guaranteed to > either find a single group or none with a matching name. Removing the > unique constraint removes that guarantee, opening up the possibility that > .get() by name will raise MultipleObjectsReturned. > > Karen
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
