On Wed, Jan 21, 2009 at 9:01 AM, Ludvig Ericson <ludvig.eric...@gmail.com>wrote:
> > On Jan 21, 2009, at 14:10, Russell Keith-Magee wrote: > > Any opinions? Any other options that I may have missed? > > Sorry if I'm stating the obvious, but would it be > impossible to error out if two aggregates cause this > unexpected behavior? > > I mean then I'd say raising an exception for such queries > would be acceptable. Something like "unsatisfiable query". > > - Ludvig > > > > Is there a way to programatically determine if an aggregate is causing such a problem(without generating false positive) and therefore we could only do the subqueries where necessary. I don't think it's fair to the users of properly working aggregates, of which there are an awful lot, to impose either unneeded restrictions or overhead. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
