Opened 3 years ago
Closed 3 years ago
#32864 closed Bug (duplicate)
When running manage.py makemigrations command, it gives an unexpected issue in check_consistent_history.
| Reported by: | Samarth_Saxena | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | 3.2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | yes |
Description
When I first create a project (even if you delete all the migration and database files), and you run python manage.py makemigrations, it gives you the following error:
C:\Users\samar\AppData\Local\Programs\Python\Python39\Lib\site-packages\django\core\management\commands\makemigrations.py: 105: RuntimeWarning: Got an error checking a consistent migration history performed for database connection default: Unable to open database file. Warnings.Warn(...)
This isn't its usual behavior as I don't have a database file and I'm working with SQLite3 and have some models in some of my apps and no migrations, so it should ideally create the database file and the migration files for me to be able to migrate into the database with manage.py migrate. However, on top throwing this warning, it doesn't create the migration files or the database file. If it helps, my code is on GitHub at http://github.com/samarth466/∴ess.git.
Change History (1)
comment:1 by , 3 years ago
| Resolution: | → duplicate |
|---|---|
| Severity: | Release blocker → Normal |
| Status: | new → closed |
Duplicate of #32865 (double form submission?)