#34398: Django should automatically run migrations on in-memory SQLite DB
-------------------------------------+-------------------------------------
Reporter: Yawar Quadir Amin | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: sqlite | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:2 Yawar Quadir Amin]:
> If we set up SQLite in-memory database as the 'live' Django database, it
should also run the migrations automatically, no?
I'm not sure how you use SQLite in-memory database in production, but if
you do this you need to handle migrations on your own. For example, by
calling `call_command("migrate", ...)` in your scripts.
--
Ticket URL: <https://code.djangoproject.com/ticket/34398#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070186c7ef8fdb-2649097c-26e7-45e1-aebd-ff91168c49ff-000000%40eu-central-1.amazonses.com.
