#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 russellm):
Replying to [comment:20 mhaligowski]:
> Personally, I think that introducing master/slave idea is too complex
for just one bug and I don't think that it will introduce any more
functionality. Having said that, I would go for the solution
'''''contenttypes/permissions go to 'default' unless stated differently in
the routers'''''. I hope I understood the idea of the routers correctly.
>
> Would someone please confirm the idea for the solution is right? If so,
I would write the solution.
I can confirm that this is almost certainly *not* the right solution.
Putting special cases into routing behaviour is something we want to
avoid. "Special cases aren't special enough to break the rules."
--
Ticket URL: <https://code.djangoproject.com/ticket/16039#comment:22>
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.
