Code

Changes between Version 65 and Version 66 of SchemaEvolution


Ignore:
Timestamp:
05/06/11 14:56:57 (3 years ago)
Author:
stormlifter@…
Comment:

Contributing to the conversation.

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolution

    v65 v66  
    416416Seems the South project (http://south.aeracode.org/) has pretty much exactly implemented what what I suggested above in this page.  
    417417-- Anders Hovmöller 
     418 
     419I 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. 
     420-- Chris Paolini