#34491: Unable to have constraints with same name on different models
-------------------------------------+-------------------------------------
Reporter: Matheus Cansian | Owner: nobody
Type: Bug | Status: closed
Component: Core (System | Version: 4.2
checks) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* cc: Simon Charette (added)
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for the report. It's true that constraints on different tables may
have the same names on PostgreSQL. However, it's not truth on other
databases. Moreover, using the same names is a rare practice when we take
into account that it has not been noticed for 4 years. I'd prefer to keep
the check for cross-database compatibility. You can always silence it by
adding `SILENCED_SYSTEM_CHECKS = ["models.E032"]` to the settings.
I hope that makes sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/34491#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701877efae6b3-8efd7d87-845b-4085-84bd-07712cb857ed-000000%40eu-central-1.amazonses.com.
