> For GIS I'm fairly certain that's broken, however I'm not quite setup > for running the GIS tests yet, therefore if you're set up for it and > can run the tests please just reply with your tracebacks here > (preferably with them on a pastebin like paste.pocoo.org though :)) > and I'll try to sort it out.
Yes, multi-db is seriously broken with GIS on all backends (it'd be pointless to list all the errors here). Basically, the massive shift of `Query` internals to `SQLCompiler` is the root of the problem -- there needs to be a corresponding `GeoSQLCompiler` with `GeoQuerySet` and `GeoQuery` wired to use it accordingly. I'll try to look at it in more detail this weekend and see if I can sketch out a better idea of what needs to be done, but so far it's looking "non-trivial." -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=.
