#32781: Made Add/RemoveConstraint operations a noop for unique constraints with
opclasses on SQLite.
-------------------------------------+-------------------------------------
Reporter: Hannes Ljungberg | Owner: Hannes
| Ljungberg
Type: Bug | Status: assigned
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
I don't think we should make it a noop. On other databases (MySQL, Oracle)
it creates a unique constraint without `opclasses` as
[https://docs.djangoproject.com/en/3.2/ref/models/constraints/#opclasses
documented]: ''"opclasses are ignored for databases besides PostgreSQL"''
and IMO expected. `opclasses` are really PostgreSQL-specific and on other
databases default operators are just fine.
--
Ticket URL: <https://code.djangoproject.com/ticket/32781#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/067.e20b74780144aa9bbc96fa4c78f70fc9%40djangoproject.com.
