Re: models: There has to be a better way.

2006-09-23 Thread [EMAIL PROTECTED]
I just do it like this Backup the table ( ehem , i usually skip this ) Change the model Run manage.py sql appname and see what fields are added. Get the table name, column name and type Then just run (postgresql, not much different in mysql i guess): alter table appname_modelname add column

Re: models: There has to be a better way.

2006-09-23 Thread [EMAIL PROTECTED]
Tom, Many of us are in the same boat. I wish that functionality was allready in Django, but for the moment it's in que. Here is a link to the Wiki entry talking about it: http://code.djangoproject.com/wiki/SchemaEvolution The SOC project has produced some code, but it needs some more

Re: models: There has to be a better way.

2006-09-23 Thread Clint Ecker
Please do a search for 'schema-evolution' on the dev list. It's been discussed ad nauseum and there was a project with Google's SoC to address the issue. The code, as far as i know, is complete and waiting in a seperate branch for testing before being merged into the main trunk. Clint On

models: There has to be a better way.

2006-09-23 Thread Tom Smith
At the moment I am learning django and so far, almost everything about it feels fantastic. Except for this...A lot of the time I need to change the database model as I go... I have millions of records and have problems dumping all the data out re-sync-ing the database and then importing the data