#34729: Add explicit option to enable IF EXISTS / IF NOT EXISTS in PostgresQL
index
operations
----------------------------------+--------------------------------------
Reporter: Laurent Tramoy | Owner: (none)
Type: New feature | Status: closed
Component: contrib.postgres | Version: 4.2
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):
* status: new => closed
* resolution: => wontfix
Comment:
I still think it is a bad idea for exactly the same reasons I already
mentioned in the #34298. Also, I don't think that separate operations or
extra arguments to control this behavior is a good idea, following this
path we could add the same to all migration operations. Why should index
creation be treated differently? Last but not least this syntax is not
supported by all database engines with built-in backends.
Please first start a discussion on the DevelopersMailingList, where you'll
reach a wider audience and see what other think, and
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#closing-tickets follow the triaging guidelines with regards to
wontfix tickets.
--
Ticket URL: <https://code.djangoproject.com/ticket/34729#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/0107018979d31574-71f793cf-b741-4a59-9d4a-5dd422570dcc-000000%40eu-central-1.amazonses.com.
