Changes between Version 61 and Version 62 of SchemaEvolution

Timestamp:

Jan 10, 2011, 1:48:09 PM (14 years ago)

Author:

Denilson Figueiredo de Sá

Comment:

Fixed numbered list formatting in "Proposal" section.

SchemaEvolution

@@ -256 +256 @@
     * ``django-admin syncdb`` applies evolutions using the following steps:
     
-        #. Makes sure evolution is installed before proceeding.
+        1. Makes sure evolution is installed before proceeding.
         
-        #. For each content type, checks that the version in the database matches
+        2. For each content type, checks that the version in the database matches
            the version in defined in the model.  For those that don't match...
            
-        #. Django looks for evolutions in ``<app_package>/upgrade/``.  Evolutions
+        3. Django looks for evolutions in ``<app_package>/upgrade/``.  Evolutions
            can either be SQL scripts named ``to_version_X.sql`` or Python scripts
            named ``to_version_X.py``.
            
-        #. ``django.contrib.evolution`` will contain utilities to abstract evolution
+        4. ``django.contrib.evolution`` will contain utilities to abstract evolution
            for different db backends.  This exact API is TBD.
            
-        #. For SQL evolutions, if a file named ``to_version_X.out`` exists, ``syncdb``
+        5. For SQL evolutions, if a file named ``to_version_X.out`` exists, ``syncdb``
            will expect the output of the evolution to match the text file EXACTLY.  If
            any differences happen, the transaction will be rolled back (for that reason