On 7/15/07, Tai Lee <[EMAIL PROTECTED]> wrote: > > I'd rather petition the PostgreSQL developers to optimise count(*) and > suggest Django users implement their own changes or workaround in the > meantime if they're working with large datasets where count(*) is a > serious performance penalty.
The two options (implement hackish exists() for PostgresSQL/etc., or petition the database developers to optimize the call) aren't mutually exclusive; we can strive for purity in the long run while dealing with the practical reality at hand. There's enough weirdness abstracted away in the db backends already; that's their point. :-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
