On Fri, 2009-04-17 at 03:19 -0700, Richard Davies wrote:
> Ticket 399 has various patches.
>
> Not clear to me why none of these have been merged for 1.1 yet?
Because it's not on the 1.1 roadmap and the time for feature additions
is long past.
Regards,
Malcolm
--~--~-~--~~---
Ticket 399 has various patches.
Not clear to me why none of these have been merged for 1.1 yet?
Richard.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email t
You could even put such an `ALTER TABLE` statement in a `sql/
modelname.sql` file to be executed as initial SQL data as soon as the
table is created by `syncdb`.
On Apr 8, 11:40 pm, Thomas Guettler wrote:
> Hi,
>
> I once get BigInt working by a little "ALTER TABLE ... ALTER COLUMN"
> statemen
Hi,
I once get BigInt working by a little "ALTER TABLE ... ALTER COLUMN" statement.
No code change for django was needed. But I have only done this once and this
application does not exist any more.
rah schrieb:
> I am Rahul.using Django0.96 from last 3 years. We are using
> BinInteger field in
I am Rahul.using Django0.96 from last 3 years. We are using
BinInteger field in one of our models. For BigInt we have added a
patch in Django. But now we want to migrate .96 to 1.0.2 .
The same problem is there in 1.0.2 it does not support to BigInt
field .The patch for 0.96 is not working with 1.
