I agree. GQL is superior from a performance perspective. You can understand what is going on under the hoord. Switching from SQL to GQL you have to rethink your model : denormalizing it. The benifits (performance and scaleability) are great and it feels good too. At the end working with GQL is even easy, without limitations which cannot be overcome.
At the moment I only use SQL (SQLite) to denormalize my SQL data. For this I need complex SQL joins. The result is a very simple model. Why have I not worked from the beginning in this way, was the first question that came up after seeing the result. The queries became far less complex. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/mA3LPE4lIuoJ. 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.
