Code

Changes between Version 30 and Version 31 of SchemaEvolution


Ignore:
Timestamp:
07/04/07 12:40:23 (7 years ago)
Author:
anonymous
Comment:

it's Django not DJango

Legend:

Unmodified
Added
Removed
Modified
  • SchemaEvolution

    v30 v31  
    385385------------------------------ 
    386386To 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 
    387 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 
     387something 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 
    388388have to know a lot, its that you have less work to do. Everything is faster, not stupider. 
    389389 
     
    392392please do not take any power or functionality away from Ben in the process.  
    393393 
    394 Also, versioning of database structure should not be the job of DJango at all. If someone wants to version their DB structure they can 
     394Also, versioning of database structure should not be the job of Django at all. If someone wants to version their DB structure they can 
    395395bust out SVN, put Django's sql output commands to use and do it themselves. Django has no business versioning anything. 
    396396