Code

Changes between Version 31 and Version 32 of SchemaEvolution


Ignore:
Timestamp:
07/16/07 15:55:38 (7 years ago)
Author:
boxed@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolution

    v31 v32  
    396396 
    397397--Rob C (rtconner) 
     398 
     399Are we going to stoop to the level of insulting hypothetical persons? :P Seriously though, Carol is not an idiot, she did the proper thing and  
     400designed what she needed what she needed when she needed it, and then changed it when that was required. This is just competent  
     401programming. Furthermore, I don't see why schema migration should be some magic fairyland object that has to be kept outside Django.  
     402Django handles databases, python is a language where you can change classes easily, and then having a system where changing some  
     403specific classes is quite a pain (like django currently) gives a kind of schizophrenic user experience. 
     404 
     405In short: Schema evolution is a part of pretty much every django developers job and should be treated with the same attitude of "let's 
     406make things non-painful" as everything else. In the case of Carol she has to write some custom code for migration though, that's inevitable. 
     407-- Anders Hovmöller 
    398408}}}