#13741: GenericForeignKey not working across multiple databases
-----------------------------------+----------------------------------------
Reporter: bartek | Owner: nobody
Status: closed | Milestone:
Component: Contrib apps | Version: 1.2
Resolution: invalid | Keywords:
contenttype,genericforeignkey
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => invalid
Comment:
Generic keys do work with multidb, and there are quite a few tests in the
multiple_database regression test to validate this.
As for point 1 -- it's impossible to diagnose further without seeing your
router. The example you provide is explicitly tested (in several variants)
in the multiple_database regression test, but the exact behavior will
depend on your router.
As for point 2 -- I can only presume you've got a custom save method that
doesn't accept the using argument, or you've somehow got a Django 1.1
install on your path somewhere. using is definititely a valid argument to
save (and, by extension, to any well defined override save method).
I'm going to mark this ticket invalid on the basis that the ticket doesn't
contain enough detail to diagnose that this is a problem and not user
error. Feel free to reopen if you can provide more diagnosis info --
sample code, including full model and router definitions would be a
minimum.
--
Ticket URL: <http://code.djangoproject.com/ticket/13741#comment:3>
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.
