From 012df8d2d35e2943cb7e115c23fea53ebf7cd849 Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Tue, 20 Oct 2020 09:49:05 +0200 Subject: [PATCH] [3.1.x] Fixed outdated notes in SchemaEditor docs. Backport of 197b55c53469cf8344d1ba35175236780cb83bd1 from master --- docs/ref/schema-editor.txt | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/ref/schema-editor.txt b/docs/ref/schema-editor.txt index 9599e877d8..0b9e0c19cd 100644 --- a/docs/ref/schema-editor.txt +++ b/docs/ref/schema-editor.txt @@ -32,12 +32,10 @@ support foreign key constraints. If you are writing or maintaining a third-party database backend for Django, you will need to provide a ``SchemaEditor`` implementation in order to work with -1.7's migration functionality - however, as long as your database is relatively -standard in its use of SQL and relational design, you should be able to -subclass one of the built-in Django ``SchemaEditor`` classes and tweak the -syntax a little. Also note that there are a few new database features that -migrations will look for: ``can_rollback_ddl`` -and ``supports_combined_alters`` are the most important. +Django's migration functionality - however, as long as your database is +relatively standard in its use of SQL and relational design, you should be able +to subclass one of the built-in Django ``SchemaEditor`` classes and tweak the +syntax a little. Methods =======