- Language: en
26 results for OneToOneField in version 2.2
-
Django Deprecation Timeline
- … OneToOneField will be required. django.db.models.fields.add_lazy_relation() will be removed. When time zone support is enabled …
-
Django 2.0 release notes
- … OneToOneField is now required in models and migrations. Consider squashing migrations so that you have …
-
System check framework
- … OneToOneField . fields.W343 : limit_choices_to has no effect on ManyToManyField with a through model. Models …
-
PostgreSQL specific model fields
- … OneToOneField and ManyToManyField ). It is possible to nest array fields - you can specify an instance …
-
Django 1.9.2 release notes
- … OneToOneField in ModelAdmin.readonly_fields ( #26060 ). Fixed a crash when calling the migrate command in a test …
-
Django 1.8.7 release notes
- … OneToOneField primary key ( #25786 ). Fixed incorrect validation for PositiveIntegerField and PositiveSmallIntegerField on MySQL resulting in values …
-
Django 1.11.1 release notes
- … OneToOneField primary key ( #28047 ). Fixed empty POST data table appearing instead of “No POST data …
-
Django 1.8.9 release notes
- … OneToOneField in ModelAdmin.readonly_fields ( #26060 ). Fixed a regression in Django 1.8.5 that broke copying a SimpleLazyObject …
-
Django 2.0.1 release notes
- … OneToOneField in ModelAdmin.autocomplete_fields ( #28898 ). Fixed a regression on SQLite where DecimalField returned a result …
-
Django 1.3 release notes
- … OneToOneField now accept an on_delete argument to customize behavior when the referenced object is deleted …
