From 7286eaf681d497167cd7dc8b70ceebfcf5cd21ad Mon Sep 17 00:00:00 2001 From: Nick Pope Date: Mon, 4 Nov 2019 13:47:58 +0000 Subject: Refs #13312 -- Simplified handling of nulls ordering on MySQL. MySQL & MariaDB support the standard IS NULL and IS NOT NULL so the same workaround used for NULLS FIRST and NULLS LAST that is used for SQLite < 3.30.0 can be used. Thanks Simon Charette for the discussion. --- django/db/backends/sqlite3/features.py | 1 + 1 file changed, 1 insertion(+) (limited to 'django/db/backends/sqlite3') diff --git a/django/db/backends/sqlite3/features.py b/django/db/backends/sqlite3/features.py index c82be5c30d..6aebbc3262 100644 --- a/django/db/backends/sqlite3/features.py +++ b/django/db/backends/sqlite3/features.py @@ -44,3 +44,4 @@ class DatabaseFeatures(BaseDatabaseFeatures): supports_over_clause = Database.sqlite_version_info >= (3, 25, 0) supports_frame_range_fixed_distance = Database.sqlite_version_info >= (3, 28, 0) supports_aggregate_filter_clause = Database.sqlite_version_info >= (3, 30, 1) + supports_order_by_nulls_modifier = Database.sqlite_version_info >= (3, 30, 0) -- cgit v1.3