Code

Changes between Version 70 and Version 71 of SchemaEvolution


Ignore:
Timestamp:
03/29/13 23:23:00 (13 months ago)
Author:
vincentwoon+django@…
Comment:

Added comment and thought about alternative command to syncdb to achieve db migration

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolution

    v70 v71  
    422422I agree with Anders Hovmöller, the type of thinking that Rob C presents belongs in another community. Django is about making things more pleasant to work with. Having to edit the schema constantly during testing is tedious and wastes time and could be handled efficiently by a SchemeEvolution system. I don't think Django would have to make it default, but if the schema change is basic there is no reason why it shouldn't behandled. I'm sorry Rob C if you pride yourself in having to write simple table edits in SQL, but Django is and always has been about allowing programmers to focus on what makes their program unique instead of having to be "hardcore" and waste time with essentially robotic tasks.[[BR]] 
    423423-- Chris Paolini 
     424 
     425Instead of relying solely on syncdb, how about suppling another command like migratedb to help with DB migration? That way, this will be an added capability on top of syncdb. [[BR]] 
     426--Vincent Woon