#34050: Generated migration file is not detected by django because of the name
of
newly generated migration file
-------------------------------------+-------------------------------------
Reporter: Bishal Gautam | Owner: Adam
| Johnson
Type: Bug | Status: closed
Component: Migrations | Version: 4.1
Severity: Normal | Resolution: fixed
Keywords: migrations | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"cd03e8e2d698e9ccefae2f7687a0400329e6cbe6" cd03e8e]:
{{{
#!CommitTicketReference repository=""
revision="cd03e8e2d698e9ccefae2f7687a0400329e6cbe6"
Fixed #34050 -- Replaced invalid chars in migration names with '_'.
Thanks to Bishal Gautam for the report and initial implementation.
Regression in fa58450a9ab8a1bdd2a5090b51b00078fd85ffa6.
Co-Authored-By: Bishal Gautam <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34050#comment:12>
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/010701837dd61bc4-1dc99ea5-fc52-4b39-8935-9f11757f6ece-000000%40eu-central-1.amazonses.com.
