#35336: Adding GeneratedField fails with ProgrammingError when using When on
CharField
-------------------------------------+-------------------------------------
Reporter: Adrian Garcia | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: postgres, | Triage Stage: Accepted
generatedfield, contains |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"888b9042b3598bab6557c62de82505eec9ea62ed" 888b9042]:
{{{#!CommitTicketReference repository=""
revision="888b9042b3598bab6557c62de82505eec9ea62ed"
Fixed #35336 -- Addressed crash when adding a GeneratedField with %
literals.
A longer term solution is likely to have a better separation of
parametrized
DDL altogether to handle checks, constraints, defaults, and generated
fields
but such a change would require a significant refactor that isn't suitable
for a backport.
Thanks Adrian Garcia for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35336#comment:7>
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/0107018ea0846e55-a58b93bc-67f0-4159-ba6f-7eac714892e4-000000%40eu-central-1.amazonses.com.
