#34955: Make available the string concatenation operator `||` for PostgreSQL
-------------------------------------+-------------------------------------
Reporter: Paolo Melchiorre | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: field, database, | Triage Stage:
generated, output_field | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* type: Bug => New feature
Comment:
> ... databases does not apply.
I don't understand why TBH. Do you want to say that it doesn't apply
because it's PostgreSQL and we should treat it specially? I would argue
with that.
This is definitively not a bug. `Concat()` is implemented this way from
the very beginning and database limitations for `GeneratedField` are
[https://docs.djangoproject.com/en/dev/ref/models/fields/#generatedfield
documented].
--
Ticket URL: <https://code.djangoproject.com/ticket/34955#comment:3>
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/0107018baeffda00-381b2beb-c339-4323-8f9e-8c8d0940168c-000000%40eu-central-1.amazonses.com.
