Code

Changes between Version 50 and Version 51 of SchemaEvolution


Ignore:
Timestamp:
02/28/09 14:17:43 (5 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolution

    v50 v51  
    381381Anders Hovmöller (boxed@killingar.net) 
    382382 
    383 A way to generate base sql migrations would fit very nicely, but automatically running them seems to be a problem. There are so many things that you have to take into consideration which Django simply can't do at present (for example, changing the type of a column that is used in a view). The best way I can see is to generate basic sql migration scripts which the developer can review before they are applied. This approach would go very well with the DbMigration project (http://www.aswmc.com/dbmigration/ - url has no such project). 
     383A way to generate base sql migrations would fit very nicely, but automatically running them seems to be a problem. There are so many things that you have to take into consideration which Django simply can't do at present (for example, changing the type of a column that is used in a view). The best way I can see is to generate basic sql migration scripts which the developer can review before they are applied. This approach would go very well with the DbMigration project (~~[http://www.aswmc.com/dbmigration/]~~ - url has no such project). 
    384384 
    385385Mike H (mike@mugwuffin.com)