#12729: contrib.auth on seperate db in multi-db setup fails ----------------------------+----------------------------------------------- Reporter: dhageman | Owner: nobody Status: new | Milestone: Component: Authentication | Version: 1.1 Keywords: multi-db | Stage: Unreviewed Has_patch: 0 | ----------------------------+----------------------------------------------- contrib.auth will break if you put it onto a database by itself. There is a hard coded SQL statement in contrib.auth.backends at line 27 (get_group_permissions) that joins the auth tables with django_content_type. This will obviously cause an error if the django_ tables are not in the same database with the auth_ tables.
-- Ticket URL: <http://code.djangoproject.com/ticket/12729> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-upda...@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
