One note on portability, for example for retrieving all objects in the datastore, sorted, in Django one could do: Poll.objects.all().order_by(...) Whereas in AppEngine it complains that order_by isn't defined, and i have to use the AppEngine's version: Poll.objects.all().order(...)
Also, when calling the following shortcut: get_object_or_404(MyDbModel, pk=my_id) It complains that pk is an unexpected argument. This is using the AppEngine helper (not the patch you linked to). I thought the AppEngine helper would make sure that the Django model methods would delegate to the AppEngine's version transparently but some seem to be missing - why is this? Bobby On Dec 15, 3:31 pm, Bobby <bobbysoa...@gmail.com> wrote: > Ah, good point about being able to make use of existing Django apps. > Thanks. > > Bobby > > On Dec 15, 2:46 pm, "Jesaja Everling" <jeverl...@gmail.com> wrote: > > > > > Well, Django doesn't really extend App Engine with more functionality, > > because you probably could do everything you could do in Django in > > webapp and vice versa. > > > > What are the main advantages of using Django on the AppEngine? > > > Well, if you ask me that would be support from the Django community > > (at least for Django related problems), a lot of reusable apps that > > will be easily portable to App Engine (in many cases you only have to > > port the model definitions, the rest should work), and independence of > > the App Engine environment. And you can make use of many of the > > shortcuts that are provided by Django to avoid repititive work. > > I think the App Engine devs chose to support Django because it is a > > great and very popular framework, and providing it will attract a lot > > of people that have experience with Django. In principle, however, > > every WSGI-compliant framework could be ported to appengine. > > If I'm informed correctly, Guido van Rossum used Django for his > > Rietveld project. > > > If you want to get as much Django-Appengine integration as possible, > > try the app-engine-patch:http://code.google.com/p/app-engine-patch/ > > > It even makes a lot of Django's generic views available in App Engine. > > > Best Regards, > > > Jesaja Everling > > > On Mon, Dec 15, 2008 at 8:58 AM, Bobby <bobbysoa...@gmail.com> wrote: > > > > Group, i'm starting work on an AppEngine site and i was going to use > > > Django (i haven't used it before), i went through the Django docs and > > > i saw lots of useful features but many exist already on the AppEngine, > > > such as database models and forms (through > > > google.appengine.ext.db.djangoforms) - plus the concept of urls and > > > views seems to be easily reproduced in AppEngine without much code. > > > > In addition to this i'm seeing that the Django admin site has been > > > replaced by the AppEngine data viewer which isn't as powerful or > > > customizable right now, so i'm not seeing alot of reasons to use the > > > Django framework (other than wanting to). > > > > What are the main advantages of using Django on the AppEngine? (i can > > > see at least two disadvantages in having an additional layer and added > > > configuration/maintenance). Was Django made compatible with the > > > AppEngine (through the Appengine Helper for Django) mostly for > > > allowing users to port their existing Django apps over or does it > > > actually extend AppEngine with added functionality? > > > > I'm probably missing something, right? Let me know, thanks.- Hide quoted > > > text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
