[Django] #32865: When running manage.py makemigrations command, it gives an unexpected issue in check_consistent_history.

[Django]

#32865: When running manage.py makemigrations command, it gives an unexpected issue
in check_consistent_history.
-------------------------------------+-------------------------------------
Reporter: | Owner: Samarth_Saxena
Samarth_Saxena |
Type: Bug | Status: assigned
Component: Core | Version: 3.2
(Management commands) |
Severity: Release | Keywords:
blocker |
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 1 |
-------------------------------------+-------------------------------------
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.

--
Ticket URL: <https://code.djangoproject.com/ticket/32865>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#32865: When running manage.py makemigrations command, it gives an unexpected issue
in check_consistent_history.
-------------------------------------+-------------------------------------

Reporter: Samarth_Saxena | Owner:
| Samarth_Saxena
Type: Bug | Status: closed
Component: Core (Management | Version: 3.2
commands) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):

* status: assigned => closed
* ui_ux: 1 => 0
* resolution: => invalid
* severity: Release blocker => Normal

Comment:

A database file is not necessary, it's created automatically by
`makemigrations`. Please use one of
[https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
support channels].

--
Ticket URL: <https://code.djangoproject.com/ticket/32865#comment:1>

[Django]

#32865: manage.py makemigrations command gives an unexpected issue in
check_consistent_history.
-------------------------------------+-------------------------------------

Reporter: Samarth_Saxena | Owner:
| Samarth_Saxena
Type: Bug | Status: closed
Component: Core (Management | Version: 3.2
commands) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

--
Ticket URL: <https://code.djangoproject.com/ticket/32865#comment:2>