6👍
✅
I had this exact same problem. Turns out that there is a circular dependency of sorts when using South. To get around this problem, don’t create a superuser when you run syncdb, but instead run:
python manage.py createsuperuser
after you have created the database with syncdb. At this point, your profile table will have been created, and the post_save signal will succeed.
0👍
Try to migrate the table without –fake option. Fake is usefull if you have changes applied in database but there are not in south_migrationhistory table.
- [Django]-Django Connection reset by peer
- [Django]-How to always prefetch_related for a specific django model
- [Django]-Fresh python 3.7 / django 2.2.1 installation not recognising that mysqlclient is installed
- [Django]-Viewflow.io: How can I present a custom form for gathering input for a specific task?
- [Django]-Django ModelForm Meta
0👍
The following should work for some people:
python manage.py schemamigration myapp --initial
python manage.py migrate myapp
- [Django]-Django application not logging request info in production log file when deployed with gunicorn and Nginx
- [Django]-Django / MySQL: How to do Autonomous Transactions (commit only sub-set of queries)?
- [Django]-Deleting files associated with model – django
Source:stackexchange.com