#34351: Slash in constraint name results in invalid migration file naming
-------------------------------------+-------------------------------------
Reporter: Simon Dupouy | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 4.1
Severity: Normal | Resolution: duplicate
Keywords: constraint name | Triage Stage:
slash | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Dupouy):
Replying to [comment:2 Dustin Wyatt]:
> I think that this never gets to the database for the database to give an
error...right? If I'm correct, I'm not sure what the appropriate fix is
(if any). I'm not sure that "databases give good error messages for this
problem" is a good resolution to a problem that databases do not give good
error messages for.
Indeed you are correct, the problem is in the way the `makemigrations`
command finds a name for the migration file. Hence it is not exactly a
duplicate issue in my opinion.
--
Ticket URL: <https://code.djangoproject.com/ticket/34351#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070186665385f3-c359d919-80e9-4ed5-a96f-36712d75b818-000000%40eu-central-1.amazonses.com.
