#399: Bigint field object needed
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: permon
Status: assigned | Component: Database wrapper
Version: | Resolution:
Keywords: sprintsept14 | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 1
----------------------------------+-----------------------------------------
Comment (by permon):
Replying to [comment:19 jacob]:
> This isn't yet ready for checkin. The MAX_BIGINT variable in
django.db.models.fields is fixed, but in reality is dependant on both
architecture and database backend. I'm not sure what the fix is, but hard-
coding 64 bits is going to look as silly in ten years as hardcoding 32
bits does today.
But we _define_ BIGINT as 64 bits long (as written in doc). So why not to
hardcode it that it will be always 64bit? Also in all db backends it is
defined as 64bit type. So, there is no same situation like with integer
data type which has always denpended on size of CPU register. This will
always be 64bits. If there is a variant that db backend cannot save 64bit
value, then we cannot us bigint type at all. But all backends supports
64bit values, so there is no problem with this. Yes, I also don't like
`magic' value, but I think that it is adequate here because python doesn't
define anything similar to sys.maxint.
--
Ticket URL: <http://code.djangoproject.com/ticket/399#comment:20>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
