OK. Agreed. By partial, I meant support for "standard" BIGINT and not the MySQL specific unsigned extension.
I will have a stab at implementing for Postgresql and sqllite and see how it goes. Cheers On Tue 10 Jul 2007, Collin Grady wrote: > Mentioned this on IRC, but just for the record here as well: It's > likely that the patch wouldn't be applied so long as it affects only > one backend - fields have to be consistent across all of them (partial > is /not/ better in cases like that). :) > > On Jul 9, 1:47 pm, Peter Nixon <[EMAIL PROTECTED]> wrote: > > Hi Guys > > > > I am a relative newcommer to the Django world (a couple of months), so > > this is my first post to the list. Let me first say how quickly I fell > > in love with the power and flexibility of Django. Keep up the good work. > > > > I have a question however. While trying to interface with an existing > > SQL table I stumbled across the problem that Django doesn't currently > > support BIGINT field types. I managed to track down a ticket in the > > tracker which has been open for for 2 year which appears to fix this > > problem: > > > > http://code.djangoproject.com/ticket/399 > > > > Is there any reason why this patch has not been applied in one form or > > another? Partial/imperfect support for BIGINT would IMHO be better than > > nothing.. > > > > Regards > > -- > > > > Peter Nixonhttp://www.peternixon.net/ > > PGP Key:http://www.peternixon.net/public.asc > > -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
