#17227: max_digits and decimal_places using "inspectdb"
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: closed
Component: Core (Management | Version:
commands) | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => wontfix
Comment:
By design, Django considers a NUMBER field with a scale of 0 as an
`IntegerField`.
This behavior was introduced in r11475 to fix #11049, and I think it's
correct. It's better to introspect `IntegerField`s created by Django as
`IntegerField`s, and occasionally misinterpret a `DecimalField` as an
`IntegerField`, than to consider all `IntegerField`s as `DecimalField`s.
--
Ticket URL: <https://code.djangoproject.com/ticket/17227#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
