Code

Changes between Version 28 and Version 29 of SchemaEvolution


Ignore:
Timestamp:
07/04/07 11:35:03 (7 years ago)
Author:
rtconner
Comment:

Add my insight into this topic

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolution

    v28 v29  
    381381 
    382382Mike H (mike@mugwuffin.com) 
     383 
     384You can't handle stupidity 
     385------------------------------ 
     386To be honest I would not like a system that tried to cater to Carol. She is an idiot and needs to learn more. If the answer to something is "you don't have to know what you are doing" then its not a good answer. DJango.. to use DJango, its not that you don't have to know a lot, its that you have less work to do. Everything is faster, not stupider. 
     387 
     388Really I'm uncomfortable catering to Alice either. If she can't read SQL, tell her not to use a database. I say start off with a system that would only cater to a know-it-all like Ben. If you can layer on ways to handle Alice/Carol later then fine do it.. but please please do not take any power or functionality away from Ben in the process.  
     389 
     390Also, versioning of database structure should not be the job of DJango at all. If someone wants to version their DB structure they can bust out SVN, put Django's sql output commands to use and do it themselves. Django has no business versioning anything. 
     391 
     392--Rob C (rtconner) 
    383393}}}