#34238 closed New feature (duplicate)
Support computed `GENERATED ALWAYS` columns
| Reported by: | Jeremy Nauta | Owned by: | Jeremy Nauta |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | generated, always, computed, field |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
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.
Proposed implementation: https://github.com/django/django/pull/16417
Change History (5)
comment:1 by , 2 years ago
| Has patch: | set |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:2 by , 2 years ago
comment:3 by , 2 years ago
| Description: | modified (diff) |
|---|
comment:4 by , 2 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | assigned → closed |
Adding a new duplicate of #31565 is not the way to move things forward. Please follow triaging guidelines with regards to wontfix tickets.
Note:
See TracTickets
for help on using tickets.
https://github.com/django/django/pull/16417