#35336: Adding GeneratedField fails with ProgrammingError when using When on
CharField
-------------------------------------+-------------------------------------
Reporter: Adrian Garcia | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution:
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
-------------------------------------+-------------------------------------
Comment (by Adrian Garcia):
Thanks for the rundown, it really helped me understand what was going on
when I followed the execution with a debugger. The ORM is easily my
favorite part of Django and it's no surprise that it is complicated as
hell, are there plans for a more unified SQL translator in a future
release? I'd be interested in following the progress of that.
I tested the fix and it works great, might not even need to use the
workaround if 5.0.4 gets released in the next few weeks. Thanks for the
speedy patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/35336#comment:5>
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/0107018e9f16c044-45fa7c91-c151-44fb-91f6-10db7bdaa0f5-000000%40eu-central-1.amazonses.com.
