#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* type: Bug => Cleanup/optimization
* resolution: => duplicate
* easy: 1 => 0
Comment:
Duplicate of #30614.
Different databases have different policies for constraint and index
names. I don't think it's worth the additional complexity as databases
throw a clear error for invalid names.
--
Ticket URL: <https://code.djangoproject.com/ticket/34351#comment:1>
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/0107018665413a60-5362477d-fbeb-4f97-9287-dbbc2025a725-000000%40eu-central-1.amazonses.com.
