… (ModelAdmin attribute) - list_editable (ModelAdmin attribute) - list_filter (ModelAdmin attribute) - list_max_show_all (ModelAdmin attribute) - list_per_page (ModelAdmin attribute) | - list_select_related (ModelAdmin attribute) - listdir() (Storage method) - lists() (QueryDict method) - listurls - django-admin command - listurls command line …
256 sections in Django dev Search all versions →
Release notes Django 1.10 release notes Backwards incompatible changes in 1.10
Django 1.8 added validation for non-relational fields in select_related(): But it didn’t prohibit nested non-relation fields as it does now:
Release notes Django 1.8 release notes Backwards incompatible changes in 1.8
select_related() now validates that the given fields actually exist. Previously, nonexistent fields were silently ignored. Now, an error is raised: The validation also makes sure that the given field is relational:
Release notes Django 1.5 release notes Features deprecated in 1.5
The depth keyword argument in select_related() has been deprecated. You should use field names instead.
Release notes Django 1.4 release notes What’s new in Django 1.4
Similar to select_related() but with a different strategy and broader scope, prefetch_related() has been added to QuerySet.
Release notes Django 1.7 release notes What’s new in Django 1.7
This enables things like filtering prefetched relations, calling select_related() from a prefetched relation, or prefetching the same relation multiple times with different querysets. See prefetch_related() for more details.
Release notes Django 6.1 release notes Features deprecated in 6.1
Calling select_related() with no arguments to select all non-nullable related fields is deprecated. Specify the related fields to fetch instead, or use the FETCH_PEERS fetch mode. Setting ModelAdmin.list_select_related to True and returning True from ModelAdmin.get_list_select_related() are deprecated.
Release notes Django 5.2.2 release notes
Fixed a crash when using select_related against a ForeignObject originating from a model with a CompositePrimaryKey (#36373).
Release notes Django 1.5.5 release notes
Fixed a Python 3 incompatibility in django.utils.text.unescape_entities() (#21185). Fixed a couple data corruption issues with QuerySet edge cases under Oracle and MySQL (#21203, #21126). Fixed crashes when using combinations of annotate(), select_related(), and only() (#16436).
Release notes Django 1.6.7 release notes
Allowed inherited and m2m fields to be referenced in the admin (#23329). Fixed a crash when using QuerySet.defer() with select_related() (#23370).
Release notes Django 1.4 release notes
… ability to bulk insert large datasets for improved performance, and QuerySet.prefetch_related, a method to batch-load related objects in areas where select_related() doesn’t work. Some nice security additions, including improved password hashing (featuring PBKDF2 and bcrypt support), new tools for cryptographic …
Release notes Django 1.6.5 release notes
Fixed the SQL generated when filtering by a negated Q object that contains a F object. (#22429). Avoided overwriting data fetched by select_related() in certain cases which could cause minor performance regressions (#22508).
Release notes Django 1.7 release notes Backwards incompatible changes in 1.7
select_related() now chains in the same way as other similar calls like prefetch_related. That is, select_related('foo', 'bar') is equivalent to select_related('foo').select_related('bar'). Previously the latter would have been equivalent to select_related('bar'). GeoDjango dropped support for GEOS < 3.1.
Release notes Django 1.7 release notes
select_related() no longer has a depth keyword argument. The get_warnings_state()/restore_warnings_state() functions from django.test.utils and the save_warnings_state()/ restore_warnings_state() django.test.*TestCase are removed. The check_for_test_cookie method in AuthenticationForm is removed. The version of django.contrib.auth.views.password_reset_confirm() that supports base36 encoded user IDs (django.contrib.auth.views.password_reset_confirm_uidb36) is removed.
Release notes Django 1.9 release notes What’s new in Django 1.9Minor features
ModelAdmin.get_list_select_related() was added to allow changing the select_related() values used in the admin’s changelist query based on the request. The available_apps context variable, which lists the available applications for the current user, has been added to the AdminSite.each_context() method.
Release notes Django 6.1 release notes Backwards incompatible changes in 6.1
choices=[("Group", [("1", "Item")]), ...]). When ModelAdmin.list_select_related is False (the default), the change list now selects only the foreign key fields specified in ModelAdmin.list_display, rather than all foreign key fields. This should improve performance for models with many foreign key fields.
Release notes Django 6.1 release notes Backwards incompatible changes in 6.1
The object-tools block is hoisted out of the content block in forms. The undocumented InclusionAdminNode.__init__() now takes the template tag name as the first positional argument. The undocumented ChangeList.has_related_field_in_list_display() method has been replaced with ChangeList.get_select_related_fields().
Release notes Django 1.5 release notes Backwards incompatible changes in 1.5
BoundField.label_tag now escapes its contents argument. To avoid the HTML escaping, use django.utils.safestring.mark_safe() on the argument before passing it. Accessing reverse one-to-one relations fetched via select_related() now raises DoesNotExist instead of returning None.
Release notes Django 1.6 release notes What’s new in Django 1.6
The list of related fields added to a QuerySet by select_related() can be cleared using select_related(None). The get_extra() and get_max_num() methods on InlineModelAdmin may be overridden to customize the extra and maximum number of inline forms.
Release notes
Added missing items to django.utils.timezone.__all__ (#21880). Fixed a field misalignment issue with select_related() and model inheritance (#21413). Fixed join promotion for negated AND conditions (#21748). Oracle database introspection now works with boolean and float fields (#19884).