#21699: Provide a way to define a model without being registered into the app
registry / Get rid of get_registered_model
------------------------------+-----------------------------------------
Reporter: mitar | Owner: nobody
Type: New feature | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: app-loading | Triage Stage: Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+-----------------------------------------
Comment (by kostko):
> mitar, how should relations (foreign keys, one to one, many to many)
between such a model and other models behave?
Do you see any specific problems here?
--
Ticket URL: <https://code.djangoproject.com/ticket/21699#comment:12>
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/063.20b549165f71fd96687b3603d4983bd6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
