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 PROTECTED]> wrote: > 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 supports > > something similar, but sqlite needs double-checking). I think, having > > 8-byte serials in Django is an even more important target than just > > having a 64-bit integer supported. > > 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 application requires BIGSERIAL, there's precisely zero > dependency on what's in Django. Just include the appropriate field > subclass in your application and use it in your model. > > Malcolm > > -- > Why be difficult when, with a little bit of effort, you could be > impossible.http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
