#16039: syncdb with --database option fails
-------------------------------------+-------------------------------------
Reporter: yedpodtrzitko | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Design
Keywords: | decision needed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
OK for me for contenttypes. I am still a bit worried about the id
mismatch. But, as said, it is likely users who have this setup will need
to know how to tackle the ID problem anyways. Permissions are a bigger
problem. To me it seems that some core parts of Django aren't ready to
handle situations where different databases give different permissions to
a user (auth/backends.py).
This ticket is out of my domain, I just don't have experience of the use
cases needing contenttypes and/or permissions in different databases so I
don't know what behavior we should be looking after.
Maybe one approach could be checking if there is any core-supported use
case for having the contenttypes/permissions in multiple databases: for
contenttypes, sure, generic foreign keys for example. For permissions - I
don't think so, auth/backends.py doesn't work and thus default
user.has_perm() doesn't work. So, what is the use case for having
permissions in more than one DB?
--
Ticket URL: <https://code.djangoproject.com/ticket/16039#comment:27>
Django <https://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-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
