Re: Ticket #399 (Bigint field object needed) status

2007-07-10 Thread Peter Nixon
I have attached my first try at a django patch (based of course on the patches in the tracker). It adds support for BigIntegerField (but not PositiveBigIntegerField) and should work on MSSQL, Oracle, MySQL, SQLite and Postgresql. Can everyone please have a look at this and see if I have made

Re: Ticket #399 (Bigint field object needed) status

2007-07-09 Thread Peter Nixon
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

Re: Ticket #399 (Bigint field object needed) status

2007-07-09 Thread Collin Grady
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]>

Ticket #399 (Bigint field object needed) status

2007-07-09 Thread Peter Nixon
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