Re: Ticket #399 -- bigint support

On Wed, Dec 16, 2009 at 1:04 PM, Karen Tracey wrote: > I've uploaded what I think is a commit-ready patch for adding > BigIntegerField.  Barring any major objections I'd like to commit this in > the next day or two. Looks good to me - go ahead. Jacob -- You received this

Re: Ticket #399 -- bigint support

I've uploaded what I think is a commit-ready patch for adding BigIntegerField. Barring any major objections I'd like to commit this in the next day or two. Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send

Re: Ticket #399 -- bigint support

In my very first Django app I ran into the int limitation and my app wouldn't work. It was quite confusing for a newbie Django user, as every other toolkit and database I have ever used supported long integers. My app integrates with Twitter, and it was the id field of tweets from Twitter that

Re: Ticket #399 -- bigint support

Gosh... copy paste was a bit fast... ti was http://code.google.com/p/django-iptocountry/ Manu -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from

Re: Ticket #399 -- bigint support

Hi, I have just subscribed and do not know how much power I'll have through my post... :) but just to let you know: I ran into the need of a bigint on postgresql installing (and refactoring a bit) http://code.google.com/p/django-countryip/ I changed the integer to bigint directly in the base

Re: Ticket #399 -- bigint support

On Wed, Dec 9, 2009 at 8:10 PM, Karen Tracey wrote: > Yes, it's easy to do yourself.  But to me this seems like an oddly basic > type to be missing from the base, with enough users potentially wanting it > that it deserves to be officially supported.  So I'd be willing to

Re: Ticket #399 -- bigint support

2009/12/10 Tomáš Kopeček > > We've fixed all issues (like incomplete tests and few bugfixes), so > patch is now ready to be included into trunk. > > I partially agree with -1 vote. It is easy. What is against: Included in > trunk we address all backends (and it looks to be easy

Re: Ticket #399 -- bigint support

> I think ticket #399 could make it into 1.2, but there's a -1 vote (from > James) to overcome first: Patch on the ticket (which is over a year old) > indicates how easy this is to do yourself if you need it. > > The patch is no longer a year old, it's been updated a few times > recently, fixing

Ticket #399 -- bigint support

I think ticket #399 could make it into 1.2, but there's a -1 vote (from James) to overcome first: Patch on the ticket (which is over a year old) indicates how easy this is to do yourself if you need it. The patch is no longer a year old, it's been updated a few times recently, fixing tests to get