Google Cloud SQL

[Bruce Aloe]

Hello,

I am a user of GAE data store and use GQL to query my models. I just
saw the article about Google Cloud SQL published on October 6, 2011.

Since GQL has so many limitations, therefore Google Cloud SQL sounds
quite interesting for me.

Where can i use it and how to use it?

Any tutorial?

Thanks for any help!

Bruce

[Brandon Wirtz]

What limitations? If you are writing your own code I think GQL is superior
to SQL, it is only if you need to use code written for SQL that it makes
sense.

It is free and you have to be a trusted tester, search the archive there are
directions that one of the Googlers posted to this list.

Hello,

Any tutorial?

Thanks for any help!

Bruce

--
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-a...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengi...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.

[voscausa]

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.

[Ikai Lan (Google)]

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 <rober...@gmail.com> 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.