| | 398 | |
| | 399 | Are 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 |
| | 400 | designed what she needed what she needed when she needed it, and then changed it when that was required. This is just competent |
| | 401 | programming. Furthermore, I don't see why schema migration should be some magic fairyland object that has to be kept outside Django. |
| | 402 | Django handles databases, python is a language where you can change classes easily, and then having a system where changing some |
| | 403 | specific classes is quite a pain (like django currently) gives a kind of schizophrenic user experience. |
| | 404 | |
| | 405 | In short: Schema evolution is a part of pretty much every django developers job and should be treated with the same attitude of "let's |
| | 406 | make 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 |