#13637: Generic Relations don't work correctly on a non-default database alias ------------------------------------------+--------------------------------- Reporter: andrewgodwin | Owner: nobody Status: new | Milestone: Component: Database layer (models, ORM) | Version: 1.1 Keywords: multi-db, truncation | Stage: Unreviewed Has_patch: 0 | ------------------------------------------+--------------------------------- Specifically, line 195 of contrib.contenttypes.generic uses django.db.connection directly - this needs to be fixed.
It looks like it will need connection-choosing pushed inside the RelatedManager provided. I'm going to work on fixing this - just noting it as a separate ticket to #13528 (I found it while fixing that, but it's a separate issue, pretty much, it affects quoting as well as table name truncation). -- Ticket URL: <http://code.djangoproject.com/ticket/13637> 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.
