Code

Changes between Version 51 and Version 52 of SchemaEvolution


Ignore:
Timestamp:
03/25/09 05:55:18 (5 years ago)
Author:
akaihola
Comment:

fixed markup for some links

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolution

    v51 v52  
    289289If 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. 
    290290 
    291 More discussion in a `django-developers thread`_ (should main points be copied here?). 
    292  
    293 .. _django-developers thread: http://groups.google.com/group/django-developers/browse_frm/thread/ec578ea4b239e844 
    294  
    295 [``brantley``: I added a proposal here at `SchemaEvolutionProposal`_.] 
    296  
    297 .. _SchemaEvolutionProposal: http://code.djangoproject.com/wiki/SchemaEvolutionProposal 
     291More discussion in a 
     292[http://groups.google.com/group/django-developers/browse_frm/thread/ec578ea4b239e844 django-developers thread] 
     293(should main points be copied here?). 
     294 
     295[``brantley``: I added a proposal here at SchemaEvolutionProposal.] 
    298296 
    299297 
     
    305303For background, let me suggest a few starting points: 
    306304 
    307  * Fowler and Sadalage's paper `EvolutionaryDatabaseDesign`_ 
    308  * `TheProcessOfDatabaseRefactoring`_ from Scott Ambler's agiledata site, which leads to the online catalog of refactorings 
    309  * and of course there's Ambler and Sandalage's book, `RefactoringDatabases`_ 
     305 * Fowler and Sadalage's paper [http://www.martinfowler.com/articles/evodb.html Evolutionary Database Design] 
     306 * [http://www.agiledata.org/essays/databaseRefactoring.html The Process of Database Refactoring] 
     307   from Scott Ambler's agiledata site, which leads to the online catalog of refactorings 
     308 * and of course there's Ambler and Sandalage's book, [http://www.bookpool.com/sm/0321293533 Refactoring Databases] 
    310309 
    311310I think there are several important advantages to this approach as compared to the one already suggested. 
     
    313312Sure, in some cases you'll have to write conversion code, but a lot of changes shouldn't require this. 
    314313If you're evolving your application by (in part) refactorings, then there's an obviously good match (object refactorings map to database refactorings). 
    315  
    316 .. _EvolutionaryDatabaseDesign: http://www.martinfowler.com/articles/evodb.html 
    317 .. _TheProcessOfDatabaseRefactoring: http://www.agiledata.org/essays/databaseRefactoring.html 
    318 .. _RefactoringDatabases: http://www.bookpool.com/sm/0321293533 
    319314 
    320315== Why something different ==