I was looking for some extremely large integers as well, so you aren't alone. Though at the moment I can't remember what I needed them for.
On Sep 2, 4:00 pm, coan <[EMAIL PROTECTED]> wrote: > For now I was planning to store ISBN13 and 13 digit ean codes. > > In mysql a bigint field would hold these, but I see no corresponing > fieldtypes in django for bigints - > the positiveintegerfield sets itself up as an int(10) signed field > type in mysql. - > I guess I could store them as charfields, but I think lookups go > faster in a bigintfield. > > On Sep 2, 9:50 pm, tchendrix <[EMAIL PROTECTED]> wrote: > > > the reason i'm asking is that digits 14 and 15 will be alphanumeric so > > add another field or two for that data (char?) and use bigint to hold > > the numerical data > > > coan wrote: > > > On Sep 2, 9:36 pm, tchendrix <[EMAIL PROTECTED]> wrote: > > > >> that looks like it's for an EAN code... how are you planning on EAN14 > > >> and EAN 15? > > > > I will take them on one digit at a time :-) > > > First I have to solve my 13 digit problem. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
