#399: Bigint field object needed
---------------------------------------------------+------------------------
Reporter: [email protected] | Owner: permon
Status: assigned | Milestone: 1.2
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
sprintsept14, bigint
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
---------------------------------------------------+------------------------
Comment (by kmtracey):
The tests from the previous patch ran on Oracle. I noticed the sqlite
problem and some of the tests were failing on MySQL and Postgres, I assume
your test tweaks involve no longer testing for the DB returning int, since
in some cases the DB is going to be returning a long? (Sorry, trac isn't
displaying the diff and I don't have much time right now.)
One thing that is not working, on Oracle, is introspection. Running
inspecdb on a table with a field created as a !BigInteger generates a
model where the field is an Integer. This is something not covered by
tests. It would be good if the tests included testing introspection. There
are a few introspection tests in regressiontests/introspection but I have
not had a chance to look at them at all to see how much guidance they give
for testing stuff like this.
--
Ticket URL: <http://code.djangoproject.com/ticket/399#comment:67>
Django <http://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.
