#34238: Support computed `GENERATED ALWAYS` columns
-------------------------------------+-------------------------------------
Reporter: jpnauta | Owner: nobody
Type: New | Status: new
feature |
Component: Database | Version: dev
layer (models, ORM) | Keywords:
Severity: Normal | generated,always,computed,field
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Hi all, I would like to propose a way to add computed (i.e. `GENERATED
ALWAYS`) database fields. This has been discussed in many different forms
over the past several years:
- [https://groups.google.com/g/django-
developers/c/9Mf7YqDA4bg/m/wb07E71oAAAJ]
- [https://code.djangoproject.com/ticket/31300]
- [https://code.djangoproject.com/ticket/31565]
The current database backend support for this feature has been thoroughly
documented by Paulo here: [https://groups.google.com/g/django-
developers/c/9Mf7YqDA4bg/m/wb07E71oAAAJ].
--
Ticket URL: <https://code.djangoproject.com/ticket/34238>
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/010701857105dba6-58e1ecb8-10f7-46f5-9f21-f72e3da3b056-000000%40eu-central-1.amazonses.com.