#34858: Output field for combined PositiveIntegerField is not properly resolved.
-------------------------------------+-------------------------------------
Reporter: Toan Vuong | Owner: Toan
| Vuong
Type: Bug | Status: assigned
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:6 Toan Vuong]:
> Still wondering about whether we need to do something about `Case`
between Postgres vs. Oracle, because the behavior still seems inconsistent
there.
`Coalesce()` on Oracle
[https://github.com/django/django/blob/d7972436639bacada0f94d3b9818446343af59ad/django/db/models/functions/comparison.py#L93
explicitly checks] the `output_field` when it's compiled (for
`Cast.default)`, on other database the `output_field` is not used when
`Coalesce()` is compiled so it doesn't crash. The crash on Oracle is a
side-effect of the current implementation, IMO, there is no need to change
it.
> Edit: Also not sure what the process is to open PRs for other
branches(?). Seems like I should also merge this to main and stable/5.0.x?
Mergers will backport if needed.
--
Ticket URL: <https://code.djangoproject.com/ticket/34858#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/0107018abbbe9d9e-bc640fcf-b004-42be-ae0e-58b91263f219-000000%40eu-central-1.amazonses.com.
