From c5cc332bf2a0b3ebfa3ad5d26c5b308de5e505be Mon Sep 17 00:00:00 2001 From: Markus Holtermann Date: Sun, 29 Mar 2015 16:59:35 +0200 Subject: Fixed #24550 -- Added migration operation description to sqlmigrate output Thanks Tim Graham for the review. --- docs/ref/contrib/gis/tutorial.txt | 3 +++ docs/ref/django-admin.txt | 6 ++++++ 2 files changed, 9 insertions(+) (limited to 'docs/ref') diff --git a/docs/ref/contrib/gis/tutorial.txt b/docs/ref/contrib/gis/tutorial.txt index c93e55ec69..ea78274781 100644 --- a/docs/ref/contrib/gis/tutorial.txt +++ b/docs/ref/contrib/gis/tutorial.txt @@ -286,6 +286,9 @@ This command should produce the following output: .. code-block:: sql BEGIN; + -- + -- Create model WorldBorder + -- CREATE TABLE "world_worldborder" ( "id" serial NOT NULL PRIMARY KEY, "name" varchar(50) NOT NULL, diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index e9dbe4b746..3515c615e7 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -984,6 +984,12 @@ By default, the SQL created is for running the migration in the forwards direction. Pass ``--backwards`` to generate the SQL for unapplying the migration instead. +.. versionchanged:: 1.9 + + To increase the readability of the overall SQL output the SQL code + generated for each migration operation is preceded by the operation's + description. + sqlsequencereset ------------------------------------------ -- cgit v1.3