Changes between Version 36 and Version 37 of SchemaEvolution

Timestamp:

Nov 13, 2007, 1:18:20 PM (17 years ago)

Author:

grimboy

Comment:

Collected existing projects and moved them to the top

SchemaEvolution

@@ +1 @@
+== Currently in progress ==
+
+[http://code.google.com/p/deseb/ http://code.google.com/p/deseb/]
+[http://code.google.com/p/django-evolution/ http://code.google.com/p/django-evolution/]
+[http://code.google.com/p/schema-evolution/ http://code.google.com/p/schema-evolution/]
+[http://code.google.com/p/django-schemaevolution/ http://code.google.com/p/django-schemaevolution/]
+[http://smileychris.tactful.co.nz/ramblings/dbevolution/ http://smileychris.tactful.co.nz/ramblings/dbevolution/]
+
+== Analysis ==
+
 Schema migration is one of those "hard" problems that I think will be impossible
 to get right for all the cases.  What follows are my thoughts on how to get
@@ -393 +403 @@
 make things non-painful" as everything else. In the case of Carol she has to write some custom code for migration though, that's inevitable.
 -- Anders Hovmöller
-
-
-
-== Implementation: Django External Schema Evolution Branch ==
-
-[http://code.google.com/p/deseb/ http://code.google.com/p/deseb/]
-
--- Derek Anderson