On Monday, 17 September 2018 08:52:32 UTC+1, Joel wrote:
>
> Thank you. That is how I fixed it yesterday late night after spending
> hours on it.
>
> For anyone else that may find it useful,
> I had dropped the tables to fix this. But that ended complaining about
> missing tables. Then I dropped
Thank you. That is how I fixed it yesterday late night after spending hours
on it.
For anyone else that may find it useful,
I had dropped the tables to fix this. But that ended complaining about
missing tables. Then I dropped the database, since all I had was
development data.
It wouldn't do the m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Joel,
On Sun, Sep 16, 2018 at 10:16:42PM +0530, Joel Mathew wrote:
> I tried to fix mysql problems in my database by dropping tables. When that
> didnt work, I dropped the database.
> I then recreated the database, and tried to run makemigrations
This is how I do it:
1. drop the database
2. create the database.
4. make sure the user identified in your settings.py can still access the
database
5. delete the migrations
6. run all migrations
Your new db should be populated with all the initial tables.
Take a look at this,
https://docs.djang
I tried to fix mysql problems in my database by dropping tables. When that
didnt work, I dropped the database.
I then recreated the database, and tried to run makemigrations. But I am
getting errors about missing tables:
joel@hp:~/myappointments$ python3 manage.py makemigrations
Traceback (most re
5 matches
Mail list logo
