Changes between Version 36 and Version 37 of SchemaEvolution


Ignore:
Timestamp:
11/13/2007 01:18:20 PM (7 years ago)
Author:
grimboy
Comment:

Collected existing projects and moved them to the top

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolution

    v36 v37  
     1== Currently in progress ==
     2
     3[http://code.google.com/p/deseb/ http://code.google.com/p/deseb/]
     4[http://code.google.com/p/django-evolution/ http://code.google.com/p/django-evolution/]
     5[http://code.google.com/p/schema-evolution/ http://code.google.com/p/schema-evolution/]
     6[http://code.google.com/p/django-schemaevolution/ http://code.google.com/p/django-schemaevolution/]
     7[http://smileychris.tactful.co.nz/ramblings/dbevolution/ http://smileychris.tactful.co.nz/ramblings/dbevolution/]
     8
     9== Analysis ==
     10
    111Schema migration is one of those "hard" problems that I think will be impossible
    212to get right for all the cases.  What follows are my thoughts on how to get
     
    393403make things non-painful" as everything else. In the case of Carol she has to write some custom code for migration though, that's inevitable.
    394404-- Anders Hovmöller
    395 
    396 
    397 
    398 == Implementation: Django External Schema Evolution Branch ==
    399 
    400 [http://code.google.com/p/deseb/ http://code.google.com/p/deseb/]
    401 
    402 -- Derek Anderson
Back to Top