SignedIntegerField / UnsignedIntegerField as part of the core fields.py
|Reported by:||Cal Leeming||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||1.3|
|Cc:||Triage Stage:||Design decision needed|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
I'd like to place a feature request to see SignedIntegerField and UnsignedIntegerField included as part of the core fields.py ( which will adhere to the 32bit limits.h defaults - http://en.wikipedia.org/wiki/Limits.h )
There has been some discussion so far in the following threads:
In terms of a use case scenario, I would imagine that most developers are used to working within the restrictions of a 32bit integer, and it would be nice to have this same ability for Django - out of the box.
If this is accepted, I'd be more than willing to submit the code and documentation patch.