#18085: sqllite integer is signed but django recognize as unsigned
-------------------------------+--------------------------------------
Reporter: robotr | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 1.4
Severity: Normal | Resolution: worksforme
Keywords: tutorial | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by msopacua):
* cc: m.r.sopacua@… (added)
* keywords: => tutorial
* component: Uncategorized => Documentation
* status: reopened => closed
* resolution: => worksforme
Comment:
I don't see how the traceback relates to your bug description. The SQL
error points to the username field, which is a character field and your
bug report mentions signed/unsigned issues with a numeric field. Many of
us have gone through the tutorial without issues so try to figure out what
you have done differently or at the very least explain how you came to the
conclusion that above traceback is caused by a signedness issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/18085#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 https://groups.google.com/groups/opt_out.
