#13637: Generic Relations don't work correctly on a non-default database alias
--------------------------------------+------------------------------------
Reporter: andrewgodwin | Owner:
Type: Bug | Status: closed
Component: contrib.contenttypes | Version: master
Severity: Normal | Resolution: fixed
Keywords: multi-db, truncation | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"aebe7800e809343d3c1a478628a25aebbad76df3" aebe780]:
{{{
#!CommitTicketReference repository=""
revision="aebe7800e809343d3c1a478628a25aebbad76df3"
[1.9.x] Refs #13637 -- Removed unused code in GenericRelatedObjectManager
Appears unused since 585b7acaa359fc1df07269c1a4b4756bdb6703f7.
Backport of 37a5a363215d7c0360ff0a8f57856d373e8c1629 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/13637#comment:10>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.214716ed6c524d63276854f2378b3215%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.