#34858: Output field for combined PositiveIntegerField is not properly resolved.
-------------------------------------+-------------------------------------
Reporter: Toan Vuong | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Toan Vuong):
Thanks for the reply! I can work on a PR for the `PositiveIntegerField`
change following the patch you wrote.
However, regarding your statement:
> Coalesce() on Oracle checks the output_field of arguments and crashes
This seems incorrect, because using `Coalesce` alone would crash on both
Postgres and Oracle. The weird thing is if I have a `Case` on top of the
"bad" `Coalesce`, then only Oracle crashes. The Postgres queryset executes
successfully. So it seems like `Case` behaves differently between the
two, and probably incorrectly swallows the error thrown by `Coalesce` in
the Postgres scenario which also seems like a bug?
--
Ticket URL: <https://code.djangoproject.com/ticket/34858#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018ab96c77ff-03ddef60-3d9d-4931-8c11-7d89ac153259-000000%40eu-central-1.amazonses.com.
