Changes between Version 51 and Version 52 of SchemaEvolution

Timestamp:

Mar 25, 2009, 7:55:18 AM (15 years ago)

Author:

Antti Kaihola

Comment:

fixed markup for some links

SchemaEvolution

@@ -289 +289 @@
 If versions are stored per-model, what happens if evolutions affect multiple models, or create or delete them? For example, in Carol's situation above, how would the individual migration scripts cooperate to move the data around in the required way? I think versions make more sense on a per-app basis; if that distinction exists in magic-removal.
 
-More discussion in a `django-developers thread`_ (should main points be copied here?).
-
-.. _django-developers thread: http://groups.google.com/group/django-developers/browse_frm/thread/ec578ea4b239e844
-
-[``brantley``: I added a proposal here at `SchemaEvolutionProposal`_.]
-
-.. _SchemaEvolutionProposal: http://code.djangoproject.com/wiki/SchemaEvolutionProposal
+More discussion in a
+[http://groups.google.com/group/django-developers/browse_frm/thread/ec578ea4b239e844 django-developers thread]
+(should main points be copied here?).
+
+[``brantley``: I added a proposal here at SchemaEvolutionProposal.]
 
 
@@ -305 +303 @@
 For background, let me suggest a few starting points:
 
- * Fowler and Sadalage's paper `EvolutionaryDatabaseDesign`_
- * `TheProcessOfDatabaseRefactoring`_ from Scott Ambler's agiledata site, which leads to the online catalog of refactorings
- * and of course there's Ambler and Sandalage's book, `RefactoringDatabases`_
+ * Fowler and Sadalage's paper [http://www.martinfowler.com/articles/evodb.html Evolutionary Database Design]
+ * [http://www.agiledata.org/essays/databaseRefactoring.html The Process of Database Refactoring]
+   from Scott Ambler's agiledata site, which leads to the online catalog of refactorings
+ * and of course there's Ambler and Sandalage's book, [http://www.bookpool.com/sm/0321293533 Refactoring Databases]
 
 I think there are several important advantages to this approach as compared to the one already suggested.
@@ -313 +312 @@
 Sure, in some cases you'll have to write conversion code, but a lot of changes shouldn't require this.
 If you're evolving your application by (in part) refactorings, then there's an obviously good match (object refactorings map to database refactorings).
-
-.. _EvolutionaryDatabaseDesign: http://www.martinfowler.com/articles/evodb.html
-.. _TheProcessOfDatabaseRefactoring: http://www.agiledata.org/essays/databaseRefactoring.html
-.. _RefactoringDatabases: http://www.bookpool.com/sm/0321293533
 
 == Why something different ==