#17854: DecimalField problem
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage:
Keywords: DecimalField bug | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by anonymous):
* component: Uncategorized => Database layer (models, ORM)
Comment:
Replying to [comment:2 anonymous]:
> Replying to [comment:1 anonymous]:
> > The database is sqlite3
> >
> > The database field (for sqlite3) is 'decimal' (when the field type in
the database is changed to say varchar(n) where n > (values to be stored
(in this case probably 202)) - everything works perfectly.
> >
> > The problem seems to be that django emits the column type as decimal
for sqlite3 (for other databases this problem is untested) instead of
varchar(max_length + probably 2)
>
> typo resolution for the above line == instead of varchar(max_digits +
probably 2)
if does not create any side effect(s) a change to this might be the
solution === django/db/backends/sqlite3/creation.py
also similar change to respective backends might be the solution (in case
a database has limits (unlike python Decimals) on the scale, precision for
its corresponding column type)
--
Ticket URL: <https://code.djangoproject.com/ticket/17854#comment:3>
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.
