Changes between Version 61 and Version 62 of SchemaEvolution


Ignore:
Timestamp:
01/10/11 13:48:09 (4 years ago)
Author:
denilsonsa
Comment:

Fixed numbered list formatting in "Proposal" section.

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolution

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