On Fri, May 4, 2012 at 9:44 PM, Will <vocalster....@gmail.com> wrote: > What does it differ from the django provided by GAE, such as django 1.2 with > Python 2.7?
Rather than alternative to GAE SDK (with Django 1.3 now) this library tries to support SDK with simple helper stuff that you need to write anyway, one way or another. > On Fri, May 4, 2012 at 12:45 PM, John Gardner <hux...@gmail.com> wrote: >> >> If you haven't seen app-engine-patch (the ancestor of django-nonrel), you >> should take a look. >> https://github.com/huxoll/app-engine-patch >> >> It's also mostly Django, but with the backend as entirely GAE. To be honest I've seen this library. I've spent some time recently developing quite a big project with django + django-nonrel. My opinion is that non-relational databases on the top of the relational ORM just don't work. You can use them for fairly simple things but when comes to slightly advance usage you will end up with problems and limitations. It's even worse when your background is Django development with SQL databases you will see them really quickly. I'm not saying that GAE storage is bad. Django ORM + GAE storage is bad idea. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
