diff options
| author | Aymeric Augustin <aymeric.augustin@oscaro.com> | 2014-06-05 17:56:56 +0200 |
|---|---|---|
| committer | Aymeric Augustin <aymeric.augustin@oscaro.com> | 2014-06-05 17:57:48 +0200 |
| commit | 342b25449d800ce29ae56ff8285869cbc3133a75 (patch) | |
| tree | 4546e9c1097c7650f0d46a4108b5e3f281808dce /django | |
| parent | 2e4bcb9b0265ceb0ef0eae6da2a91f89d037d05f (diff) | |
[1.7.x] Added a flag for the ability to introspect nullable fields.
Previously this was conflated with another Oracle-specific behavior.
Backport of a03d38d from master.
Diffstat (limited to 'django')
| -rw-r--r-- | django/db/backends/__init__.py | 3 | ||||
| -rw-r--r-- | django/db/backends/oracle/base.py | 1 |
2 files changed, 4 insertions, 0 deletions
diff --git a/django/db/backends/__init__.py b/django/db/backends/__init__.py index 90d99b14cc..e3f6266574 100644 --- a/django/db/backends/__init__.py +++ b/django/db/backends/__init__.py @@ -663,6 +663,9 @@ class BaseDatabaseFeatures(object): # Can the backend determine reliably the length of a CharField? can_introspect_max_length = True + # Can the backend determine reliably if a field is nullable? + can_introspect_null = True + # Confirm support for introspected foreign keys # Every database can do this reliably, except MySQL, # which can't do it for MyISAM tables diff --git a/django/db/backends/oracle/base.py b/django/db/backends/oracle/base.py index de264a7b5b..f7790415db 100644 --- a/django/db/backends/oracle/base.py +++ b/django/db/backends/oracle/base.py @@ -112,6 +112,7 @@ class DatabaseFeatures(BaseDatabaseFeatures): supports_tablespaces = True supports_sequence_reset = False can_introspect_max_length = False + can_introspect_null = False can_introspect_time_field = False atomic_transactions = False supports_combined_alters = False |