#35147: Document that non-wrapped arithmetic with integer fields might require
explicit output_field
-------------------------------------+-------------------------------------
Reporter: Petar Netev | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 5.0
Severity: Normal | Resolution:
Keywords: annotate, bitand, | Triage Stage: Accepted
filter, integerfield, overflow |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Replying to [comment:6 Petar Netev]:
> Hi Natalia and Simon,
>
> I would like to prepare the patch, but I would need some clarifications
on it.
>
> - Do we refference the release notes for version 5.0, specifically
https://docs.djangoproject.com/en/5.0/releases/5.0/#models ?
> - Do we refference the documentation of the F()
https://docs.djangoproject.com/en/5.0/releases/5.0/#models ?
>
> Simon, can you share the commit related to "I'm fairly certain this
relates to a commit meant to address a SQLite crash and a DDOS vector on
Postgres only present in 5.0" in order to mention it in the docs
improvements?
dde2537fbb04ad78a673092a931b449245a2d6ae is the commit I was referring to,
we don't refer to commits or ticket numbers in docs though.
I think the existing documentation is clear enough that
`ExpressionWrapper` might be necessary in these cases, the only admonition
I would add, assuming we believe it might be valuable is a note in
[https://docs.djangoproject.com/en/5.0/releases/5.0/#miscellaneous the
miscellaneous section] of the 5.0 release notes mentioning that explicit
`ExpressionWrapper` wrapping might be necessary for integer field
arithmetic that can overflow while it wasn't the case in previous release
by referencing at the documentation mentioned in comment:2.
--
Ticket URL: <https://code.djangoproject.com/ticket/35147#comment:9>
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/0107018d583824a3-0a777954-36c5-445f-a780-7637f0d7898c-000000%40eu-central-1.amazonses.com.
