Hi again,
can you verify that there are two migration scripts in your migrations
folder?
if yes, did you run manage.py migrate after the initial fake migration?
if not, i speculate, that you ran south only after you already changed
the models to include the aa column.
South needs to know the initial state of your models to calculate the
difference in the schema.
If this is the case, you now have multiple options to recover:
Option 1: simply add the aa column to the db manually. New migrations
should work fine after that.
Option 2:
-remove the migration scripts.
-Drop all the south tables.
-Remove the aa field in your model.
-syncdb to create the south tables
-Use the convert_to_south command
-add the aa field again
-do a schemamigration
-migrate
hendrik
P.S: the database you are using shouldn't matter...
On 06/10/2012 09:14 PM, Raitucarp wrote:
@henzk
I still get the error, when access admin:
DatabaseError at /admin/ngobrol/ngobrol/
no such column: ngobrol_ngobrol.aa
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/m0OH9jRnXWkJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
