#23348: Changes in Django 1.7 break nested Applications
--------------------------------------+--------------------
Reporter: glassresistor | Owner: nobody
Type: Uncategorized | Status: new
Component: Core (Serialization) | Version: master
Severity: Release blocker | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
Currently applications like django-oauth2-provider which include nested
applications for organizational reasons now break in 1.7.
Causing errors like
DeserializationError: Problem installing fixture '/home/mike/code/django-
oauth2-provider/provider/oauth2/fixtures/test_oauth2.json': Invalid model
identifier: 'oauth2.client'
The issue is that dev now names this provider_client instead of
oauth2_client within the database itself.
I've gone through and manually set the db_table to what it would be in 1.6
and am still getting the serialization error on the fixture because oauth2
doesn't exist as an application.
Its not clear if the solution is to make it act like 1.6 in these cases or
to better document the compatibility difference.
--
Ticket URL: <https://code.djangoproject.com/ticket/23348>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.97e68938764411b683d10215dcefb7fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
