#36875: Avoid unnecessary Coalesce in Concat/ConcatPair
-------------------------------------+-------------------------------------
Reporter: David | Owner: Rusheel
Type: | Chandra Reddy
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: concat,coalese | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David):
Hi Simon, I understand that there are other things which relies on
`COALESCE` to work, expecially in cross-database context where things can
break quite easy.
My proposal is to start by addressing the case in which it is involved a
`Value`, where it is simple to detect if it is/not NULL, thus avoiding the
`Coalesce(Value("a"), Value(""))` path.
Yet I realize that this may be a breaking change for people who relies con
`Concat` in their index/constraints and could be affected, however I
belive that it can be an improvement.
--
Ticket URL: <https://code.djangoproject.com/ticket/36875#comment:4>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019be17243bc-44d8e44e-6272-43bc-b247-9d3fe258921b-000000%40eu-central-1.amazonses.com.
