Hi Wesley, Maybe it would also be helpful to point out in advance what known behaviors (often considered as limitations) of the datastore will be carried to the MySQL compatibility layer that Django would have to deal with.
For example, currently using GQL counting the number of rows returned by a query is/was really tricky because of the 1000 rows limit. I also recall there was a 1 MB limit on the size of every item you could store. I've collected some links regarding this kind of stuff that I'm including here: http://aralbalkan.com/1504 http://stackoverflow.com/questions/421751/whats-the-best-way-to-count-results-in-gql http://stackoverflow.com/questions/264154/google-appengine-how-to-fetch-more-than-1000 http://stackoverflow.com/questions/703892/whats-your-experience-developing-on-google-app-engine http://blog.burnayev.com/2008/04/gql-limitations.html Hope this help a bit discuss this matters, Antonio Lima-Peru -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
