- Language: en
30 results for OneToOneField in version 5.1
-
Django 1.7 release notes
- … OneToOneField for Multi-table inheritance are now discovered in abstract classes. It is now possible …
-
System check framework
- … OneToOneField . fields.W343 : limit_choices_to has no effect on ManyToManyField with a through model. This …
-
Django 2.0 release notes
- … OneToOneField is now required in models and migrations. Consider squashing migrations so that you have …
-
Django Deprecation Timeline
- … OneToOneField will be required. django.db.models.fields.add_lazy_relation() will be removed. When time zone support is enabled …
-
Django 1.3 release notes
- … OneToOneField now accept an on_delete argument to customize behavior when the referenced object is deleted …
-
Django 1.11.1 release notes
- … OneToOneField primary key ( #28047 ). Fixed empty POST data table appearing instead of “No POST data …
-
Django 4.2.2 release notes
- … OneToOneField reference ( #34612 ). Fixed a bug in Django 4.2 where makemigrations --update didn’t respect …
-
The Django admin site
- … OneToOneField , and ManyToManyField fields. ModelAdmin. preserve_filters By default, applied filters are preserved on the list …
-
PostgreSQL specific model fields
- … OneToOneField and ManyToManyField ) and file fields ( FileField and ImageField ). It is possible to nest array …
-
Django 1.7.4 release notes
- … OneToOneField to a ForeignKey ( #24163 ). Prevented the static.serve view from producing ResourceWarning s in certain …
