Positive integer fields are useful all the time, and BigIntegerField
is no exception to that.

On a side note, there doesn't appear to be any built-in model-field
level protection from putting gigantic numbers into an IntegerField.
When using IntegerField in dev (sqllite3) it allows me to put
something like 5000000000000000000000000 without raising an error.
When saved this way the output of that field is rendered as -1. I
don't know the science behind this however, but imagine it has to do
with deserializing into a long int.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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-developers?hl=en.

Reply via email to