#32563: Cannot override database used with RelatedManager
-------------------------------------+-------------------------------------
Reporter: Lucas Gruber | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: RelatedManager | Triage Stage:
mullti databases | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Lucas Gruber):
Hello,
I do not understand your response. I do not ask for helping...
All method and all other objects in database layer allow to override
database because else, it not possible to use custom migration with
multiple databases.
Only one case does not allows this functionality : it is this case with
RelatedManager...
There is no solution for using custom migration with database router in
the current version of Django. I have overridden this bug currently by
exploiting a static variable that I manually modify in the database
migration to force my router to use the database without relying on the
sites application.
So yes, i think it is a bug and there is no a clean solution with actual
code.
Please could you reconsider closing this ticket ?
--
Ticket URL: <https://code.djangoproject.com/ticket/32563#comment:4>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.71d08d60d28702c4048344233a43dc2a%40djangoproject.com.
