#35732: Postgresql Concat using || and Trigram similarity operator precedence
bug
-------------------------------------+-------------------------------------
Reporter: Gastón Avila | Owner: Gastón
| Avila
Type: Bug | Status: closed
Component: contrib.postgres | Version: 5.1
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"590f5e09f001736aa1fe3f7f086f8a5ab5e4bfdb" 590f5e0]:
{{{#!CommitTicketReference repository=""
revision="590f5e09f001736aa1fe3f7f086f8a5ab5e4bfdb"
[5.1.x] Fixed #35732 -- Wrapped ConcatPair expression in parentheses to
ensure operator precedence.
When ConcatPair was updated to use || this lost the implicit wrapping from
CONCAT(...).
This broke the WHERE clauses when used in combination with PostgreSQL
trigram similarity.
Regression in 6364b6ee1071381eb3a23ba6b821fc0d6f0fce75.
Backport of c3ca6075cc0ad425bcf905fe14062f38eb9fbcbf from main.
Co-authored-by: Emiliano Cuenca
<[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35732#comment:8>
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/01070191e11a3c45-de649ce9-cac9-4916-a643-919db9c9520b-000000%40eu-central-1.amazonses.com.
