Most of the time in the majority of application this causes major
slowdowns and timeouts resulting in bad user experience.
To override this behaviour you have to specify `ModelAdmin.raw_id_fields`
manually so the all of the foreign objects won't be fetched and page will
be loaded quickly. Since majority of applications only benefit from using
raw_id_fields, developers need to write boilerplate code for every
ModelAdmin with related keys.
Since just making raw id field widgets a default option may be a backward-
incompatible change that may affect all of the users, I propose to add an
setting that changes the default behaviour of this widget in admin site
e.g. `ADMIN_RAW_ID_FIELDS` which is set to `False` by default. Setting
this option to `True` will render all foreign keys as `raw_id_fields` by
default saving a lot of time on writing boilerplate code on every
migration involving Models with foreign keys that are rendered in Admin
site.
--
Ticket URL: <https://code.djangoproject.com/ticket/31775>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => duplicate
Comment:
This would be solved by an implementation for #17881.
--
Ticket URL: <https://code.djangoproject.com/ticket/31775#comment:1>