I'm a bit more familiar with Django than I am with App engine, and I think that Django would make my application more readily portable. The main reason, though, was that I felt that WebApp wasn't quite able to handle any non-trivial applications. It sounds like there are some alternatives, so I'll look in to those.
Ellie On Aug 23, 12:17 am, Kyle Finley <[email protected]> wrote: > Hi Ellie, > > I'm assuming you talking about native Django models. I began a port of > GeoModel to Django-norel some time ago, but never completed it. Here's the > repo django-geomodel <https://bitbucket.org/scotch/django-geomodel>. I found > that for my dataset, without async support in Django, the queries were > extremely slow. If you weren't using the async version with db models, or > your doing bounding box queries, it might work for you, though. > > For the GeoPt Property I used the ListField from > djangotoolbox<https://bitbucket.org/wkornewald/djangotoolbox> > . > > If you don't mind me asking, why the move? I've actually moved from > django-nonrel to webapp2 <http://code.google.com/p/webapp-improved/> for > greater efficiency, so I'm curious. > > - Kyle -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
