#16281: ContentType.get_object_for_this_type using wrong database for creating
object
-------------------------------------+-------------------------------------
Reporter: tfrydrychewicz@… | Owner: poirier
Type: Bug | Status: new
Component: | Version: master
contrib.contenttypes |
Severity: Normal | Resolution:
Keywords: contenttype, object | Triage Stage: Accepted
get_object_for_this_type, |
database, multiple |
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by gregplaysguitar):
I've just been bitten by this bug (django 1.7) - I have a particular app
in a separate database, and now the admin's "view on site" link doesn't
work because it's looking for the object in the default database. What are
the chances of it being addressed?
I don't really think this is an edge case; as it stands the "view on site"
link will fail for *any* object kept in a separate database, and the only
way to remove said link is to remove the get_absolute_url method from the
model.
--
Ticket URL: <https://code.djangoproject.com/ticket/16281#comment:13>
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/082.607a620fee38cfc149975a6355bdad85%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
