summaryrefslogtreecommitdiff
path: root/django
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2018-03-16 10:21:13 -0400
committerTim Graham <timograham@gmail.com>2018-03-16 11:43:41 -0400
commitf8b98f0edc501ca1ca2d04d1d5938cbb68d11db5 (patch)
treeb8e8c7e7abf1f38fdd58853ca4d3ec21855b4573 /django
parent362813d6287925b8f63f0b107c55a74d95f5825e (diff)
Removed DatabaseFeatures.can_introspect_null.
The only known usage is in the unmaintained django-pymssql project.
Diffstat (limited to 'django')
-rw-r--r--django/db/backends/base/features.py9
1 files changed, 1 insertions, 8 deletions
diff --git a/django/db/backends/base/features.py b/django/db/backends/base/features.py
index 9a349ed8c0..7d3078c1f8 100644
--- a/django/db/backends/base/features.py
+++ b/django/db/backends/base/features.py
@@ -109,13 +109,6 @@ class BaseDatabaseFeatures:
# Does the backend reset sequences between tests?
supports_sequence_reset = True
- # Can the backend determine reliably if a field is nullable?
- # Note that this is separate from interprets_empty_strings_as_nulls,
- # although the latter feature, when true, interferes with correct
- # setting (and introspection) of CharFields' nullability.
- # This is True for all core backends.
- can_introspect_null = True
-
# Can the backend introspect the default value of a column?
can_introspect_default = True
@@ -286,6 +279,6 @@ class BaseDatabaseFeatures:
introspection results; it should provide expectations, not run an
introspection itself.
"""
- if self.can_introspect_null and field and field.null:
+ if field and field.null:
return 'NullBooleanField'
return 'BooleanField'