On Apr 25, 2008, at 9:22 PM, Malcolm Tredinnick wrote:
> Hold on. One of the reasons a fair bit of effort was put into making
> it
> much easier to subclass model fields is so that we don't have to play
> this endless game of adding every type of specialised field under the
> sun.
>
> If your a
I fixed all these problems for me already, Malcolm; but it seems it
may be confusing for some people that Django does not support more
than 4.2G entries in a table out-of-the-box, without such specific
tuning. 4.2G is a really not that large number.
On 26 апр, 06:22, Malcolm Tredinnick <[EMAIL PR
On Fri, 2008-04-25 at 15:12 -0700, Alex Myodov wrote:
> I am among the people interested in this patch.
> But, looking at the patch concepts from the PostgreSQL perspective, I
> wonder whether it will be possible to use it as a base of native
> BIGSERIAL support in Django (it is likely that MySQL
I am among the people interested in this patch.
But, looking at the patch concepts from the PostgreSQL perspective, I
wonder whether it will be possible to use it as a base of native
BIGSERIAL support in Django (it is likely that MySQL supports
something similar, but sqlite needs double-checking).
Ivan,
Thanks for the idea.
cheers
Darren
Ivan Sagalaev wrote:
Darren Redmond wrote:
I could not find any way to make the Integer Field use the int8 type
without changing the django db mappings code,
I once hacked it with initial SQL that changed column type after
creation:
ALTER
Darren Redmond wrote:
I could not find any way to make the Integer Field use the int8 type
without changing the django db mappings code,
I once hacked it with initial SQL that changed column type after creation:
ALTER TABLE "table" DROP COLUMN "column";
ALTER TABLE "table" ADD COLUMN
Felix Ingram wrote:
> On 8/22/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> >
> > I'd like an integer field larger than postgresql's integer (2^31).
> >
> > Any interest in a patch for BigIntegerField?
>
> Matt Croydon submitted a patch a while ago:
> http://code.djangoproject.com/ticket/399
>
> I
I have wanted this as a built in "Type" for some time. I usually just
do some manual SQL to alter the columbs that I need to be "Big
Integers", but it would be nice to have them built in, especially for
the default row id created for each table. Hopefully this will make
its way into the trunck
On 8/22/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> I'd like an integer field larger than postgresql's integer (2^31).
>
> Any interest in a patch for BigIntegerField?
Matt Croydon submitted a patch a while ago:
http://code.djangoproject.com/ticket/399
It might need a bump.
Felix
--~--~---
