django-reset-migrations | Add one command to reset the django migrations | Data Migration library

I ran into an annoying issue today during the development of a Django project where I was attempting to move between a testing database and a development database, and I cannot seem to figure out a solid way to go about fixing issues with migrations.

Let's call my 'test' DB: testDB and my 'dev' DB: devDB

I was accessing testDB as usual through Django settings.py and I made migrations adding the clientID field you see in the code below.

Then, I decided to swap to devDB in my Django's settings.py to run python manage.py migrate, and my clientID field is not added to the new DB. When I run python manage.py makemigrations I get, as expected, "no changes detected".

Just so this is noted, I am using the django-reset-migrations package from PyPi after I make migrations so the migrations folder does not get complicated and everything is stored in a single 0001_initial.py migrations file.

I am not seeing a better way to handle this issue than by writing my own script that ensures all Model tables exist in whatever DB I am connected to, and that all Model fields are located in each table, else the table is altered and the appropriate columns are added, which brings me to my question...

If I use: python manage.py sqlmigrate objects 0001 (which is my 0001_initial.py file), I am presented with the creation code below: