Ariel, > Is it a gis issue or an aggregation one?
As I indicated in private correspondence, this was a matter of updating GeoQuery.get_columns to reflect Russell's aggregation changes. I've attached to #3566 a patch for Russell's git repo that fixes the problem (geoquery_aggregation_fix.diff). For posterity, I'll repeat my previous message: While the gis tests pass, I'm not sure of the consequences when mixing aggregate functionality w/geo functionality -- if you could play around and note what works and what doesn't it'd be great. I'm sure lots of GeoQuerySet methods may be simplified through the use of Russell's API (obvious examples include my own geo-aggregates). If you're ambitious, take a look into this if you can; otherwise I'll get around to deeper inspection of the source the some day. Best Regards, -Justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
