From 61d783f3d7c9d4c7a0ac05f7fbbaba78e5cef5aa Mon Sep 17 00:00:00 2001 From: Florian Apolloner Date: Sun, 10 Aug 2014 13:31:06 +0200 Subject: [PATCH] Made sqlite's remove_field behave like the base backend. --- django/db/backends/sqlite3/schema.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/django/db/backends/sqlite3/schema.py b/django/db/backends/sqlite3/schema.py index 85aaaa1af46..4ea5ecf0a08 100644 --- a/django/db/backends/sqlite3/schema.py +++ b/django/db/backends/sqlite3/schema.py @@ -172,6 +172,9 @@ class DatabaseSchemaEditor(BaseDatabaseSchemaEditor): # For explicit "through" M2M fields, do nothing # For everything else, remake. else: + # It might not actually have a column behind it + if field.db_parameters(connection=self.connection)['type'] is None: + return self._remake_table(model, delete_fields=[field]) def _alter_field(self, model, old_field, new_field, old_type, new_type, old_db_params, new_db_params, strict=False):