When I click in my table in http://127.0.0.1:8000/admin/, I see this error:
OperationalError at /admin/home/table/
no such table: home_table.
I ran Python manage.py makemigrations home, Python manage.py makemigrations and Python manage.py migrate but they didn't work.
If you're using sqlite then:
Try unapply all the migrations using using command:
python manage.py appname zero
Then apply the migrations command again. If it still doesn't work then delete your sqlite db and run migrations again. It will work.
Related
I deleted a model in Django which I created for testing purposed. Now when I try and run makemigrations and mirgrate I get the following error:
django.db.utils.ProgrammingError: table "members_test" does not exist
Is there a standard procedure I should be doing when deleting a model? I only deleteed the code out of my Models file and tried migrating after.
I've only tried runing migrate and make migrations in addtion to scouring the web.
Simply you can delete all migrations folder and re-migrate using below command:
python manage.py makemigrations appname
python manage.py sqlmigrate appname 0001
python manage.py migrate
I have made migrations still i am getting this error . I have tried deleting the database and making it again. I have tried making migrations again and again but problem is still there.
OperationalError at /admin/login/
no such table: auth_user
Note
python manage.py makemigrations
python manage.py migrate
i have used both
Try deleting the migrations folder but don't delete init.py file. After this, run the commands:
python manage.py makemigrations
python manage.py migrate
I'm using PostegreSQL.
What I've tryed already:
python manage.py flush
python manage.py makemigrations
python manage.py migrate
python manage.py makemigrations app
python manage.py migrate app
python manage.py migrate --run-syncdb
There aren't any effect. The table have no recently added columns.
Have no importaint data in tables, can remove it.
Delete all migration files (except the init.py files) and database, rerun makemigrations and migrate.
Remove all DB tables.
Remove all migration files from migrations directory.
python manage.py makemigrations
python manage.py migrate
I've dropped my Postgres database by accident. Then as per this solution I deleted the migration files but now can't execute the third step's command "python manage.py migrate --fake".
RuntimeError: Error creating new content types.
Please make sure contenttypes is migrated before trying to migrate apps individually.
psycopg2.ProgrammingError: relation "django_content_type" does not exist
LINE 1: ..."."app_label", "django_content_type"."model" FROM "django_co...
^
I tried running "python manage.py migrate contenttypes" and "python manage.py makemigrations contenttypes --empty" but neither work.
Using django 1.9.5
Synchronise your project first:
like this:
python manage.py syncdb
when finish you can run: python manage.py makemigrations and last python manage.py migrate
I have a production web project running with a decent amount of data in the MySQL db. I am trying to update the database with some changes to an app called "enterlink." I've made new elements in the existing models and created new models altogether. Before this migration, I have never touched the schema of the db since originally running syncdb to create it. When I run: "python manage.py makemigrations enterlink" the below output appears(pic). My question is, why is this happening? The DB already includes all the models that it lists in the picture so why is it registering those lists of models? When I go to finish the migration by doing "python manage.py migrate" or "python manage.py migrate --fake enterlink" (pic again), I get an output shown but my database schema remains identical to the old db and any new code generates errors. Can anyone tell me what is likely the problem? I would be really appreciative of any advice. It's been very frustrating since I'm not sure what I'm missing.
What you have done is that you have ran the command python manage.py syncdb before running python manage.py makemigrations myapp and python manage.py migrate myapp. That is why syncdb created the database schema and the migration was faked because schema already exists. I will suggest to use python manage.py makemigrations myapp and python manage.py migrate myapp and not to use syncdb as its deprecated in Django 1.7.
If you change anything in your model, just run makemigrations and migrate command. Syncdb isn't necessary.
This question and relevant answers are intriguing me. Thus I want to share my experience on maintaining live database and migrations.
Tested in django1.5.5
Initializing the database:
./manage.py syncdb --noinput
./manage.py migrate
./manage.py syncdb
Now I have created the database.
Doing a migration for an app:
./manage.py schemamigration myapp --initial
./manage.py migrate myapp --fake
Now do necessary changes in your model
./manage.py schemamigration myapp --auto
./manage.py migrate myapp
Im newbie for schemamigration too, but i will explain how it works for me:
First you create app and then
./manage.py sycndb, so tables are created then you can
./manage.py makemigrations myapp --initial
so now initial migrations are created and you should apply them
./manage.py migrate myapp
now you can change your models : add,change fields, anything you want and then
./manage.py makemigrations myapp --auto
this will create migrations for changes and now you need to apply them
enter code here./manage.py migrate myapp
so this actually will create new tables in db