I thought that it was fixed along with https://code.djangoproject.com/ticket/12344 ... Bascially it aoubt that Django picks "origin manager" to be used in related models (and thus related model manager) as well and that seem to cause queries to fail.
On Sun, Jul 1, 2012 at 3:42 AM, Ethan Jucovy <ethan.juc...@gmail.com> wrote: > On Sat, Jun 30, 2012 at 8:31 PM, Odagi <fcmira...@gmail.com> wrote: > >> It's working! Thanks a lot. >> Is There a problem with mixing regular models fields with geomodels ones? >> > > No, there's no problem, as long as you remember to use a GeoManager on > every model that ever does geospatial queries (whether or not it has any > geospatial fields itself) > > -Ethan > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- Jani Tiainen - Well planned is half done, and a half done has been sufficient before... -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
