What you're trying to do is called "Schema migration" or "evolution"
there's been a lot of talk of it in the past. I recommend the South
project for evolution. Very very flexible. Check it out here:
http://south.aeracode.org/
On Apr 17, 1:30 am, Rama Vadakattu
OR you can use django-evolutions which evolves the database schema in
sync with the models.
More details at : http://code.google.com/p/django-evolution/
On Apr 17, 10:29 am, zayatzz wrote:
> If the tables of this app hold no info, then you can do python
> manage.py
If the tables of this app hold no info, then you can do python
manage.py reset appname. This clears all tables of this app but the
changes will hit database :)
Alan
On Apr 16, 7:11 pm, Aneesh wrote:
> This is by design. syncdb only checks to see if it needs to
On Apr 16, 11:00 am, gry wrote:
> [django: 1.1 beta 1 SVN-10407, python 2.5.2, ubuntu]
> My first django toy app. I've been working through the
> tutorialhttp://docs.djangoproject.com/en/dev/intro/tutorial02/.
> I've already done a few cycles of (change-model,
This is by design. syncdb only checks to see if it needs to create
any new DB tables for any models; it does NOT alter existing model
tables. See http://docs.djangoproject.com/en/dev/ref/django-admin/#syncdb
for more info.
If you don't have any valuable data in the table (ie, you're just
[django: 1.1 beta 1 SVN-10407, python 2.5.2, ubuntu]
My first django toy app. I've been working through the tutorial
http://docs.djangoproject.com/en/dev/intro/tutorial02/.
I've already done a few cycles of (change-model, ./manage.py syncdb)
with success.
I just added email and birthday fields
6 matches
Mail list logo