#34050: Generated migration file is not detected by django because of the name
of
newly generated migration file
-------------------------------+-----------------------------------------
Reporter: Bishal Gautam | Owner: Bishal Gautam
Type: Bug | Status: assigned
Component: Migrations | Version: 4.1
Severity: Normal | Resolution:
Keywords: migrations | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+-----------------------------------------
Comment (by Bishal Gautam):
Yes, as an experiment, I changed the name of constraint by putting `*` in
the file name. Django created the file name with the exact name of the
constraint but failed to create a migration file because of invalid name
of file. I have also added an attachment for this. Kindly find above.
- This didnot create a migration file and generated a error from django
core. I think it still tells the user that the invalid file name causes
this issue.
- In case of dot `.` , migration file was created everytime. Generated
migration file was getting replaced by new one. Django was not able to
find the migration file using `migrate` command. So I think this dot
character error is a bit misleading to users and needs to be replaced.
Or may be we can replace most of the frequently used invalid character if
replacing doesnot compromise the performance of project.
--
Ticket URL: <https://code.djangoproject.com/ticket/34050#comment:2>
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/0107018373949997-68b2ce8a-299e-4466-90e2-36f5691ea1e9-000000%40eu-central-1.amazonses.com.
