Thanks Robert and Brandon!

I was really concerned that making Cloud SQL available would cause people to
try to fit everything into a SQL peg instead of trying to think what the
best persistence model is. SQL is really good for some things, but so is the
datastore. I think the true sweet spot for apps going forward will be some
hybrid of SQL and datastore usage, but it's hard to publish best practices
that are along the lines of "think out the problem first".

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com | twitter.com/ikai



On Fri, Oct 14, 2011 at 6:45 AM, voscausa <[email protected]> wrote:

> 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 [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.
>

-- 
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.

Reply via email to