Hm, actually, he's talking about Java, where the situation is completely different. AFAIK there is *another* SQL-like language (this one much closer to "real" SQL) that is part of a standard (not App Engine specific) way of accessing databases. IIUC this is part of JDO -- search for Datanucleus and SQL and you'll find it. JDO and Datanucleus are not App Engine specific (and not written by us). However in App Engine certain queries (e.g. Joins) are not supported. But I don't think we have the option of not calling it SQL.
Still, thanks for forwarding this -- I do understand that GQL is controversial (several users have already pleaded to keep it). --Guido On Mon, Jan 17, 2011 at 21:01, Robert Kluin <[email protected]> wrote: > Guido, > Just wanted to point this post out, it is a good example of what > several people recently mentioned about GQL and how it leads to > confusion with SQL. > > I think this line summarizes some people's confusion well: > "use them with googles app engine sql language." > > > I don't have any good suggestions for a solution, since I know many > people really like *G*QL. Other than maybe changing the name to > something not SQL sounding, maybe... EFL -- Entity Finding Language > ... :) > > > > Robert > > > > > > On Mon, Jan 17, 2011 at 10:11, Steel City Phantom <[email protected]> wrote: >> im writing a new app. currently its a LAMP app, heavy on AJAX, but once >> this prototype is done and running i want to rewrite it as an enterprise >> level application. im looking at GAE as a back end (more because ive never >> done it before and it looks cool than anything else, free hosting doesn't >> hurt either) but im struggling with the data store stuff. the biggest >> problem i have so far is changing the data store once its deployed. here is >> what i understand so far, tell me where im wrong cuz im sure i am >> 1 - create your entity objects (this is java) >> 2 - when deployed, GAE will create the data store based on the entity >> objects in your WAR file. >> 3 - use them with googles app engine sql language. >> now, if i want to change the model >> update your entity objects with your new fields or whatever and deploy. now >> GAE should maintain the existing data and update the objects. >> or am i completely off base in thinking like a relational database system. >> is it more as a base relational system that stores blobs and i can store >> whatever i want in them? >> second, >> what if i have a drastic change to the data model that requires some >> translation sql to implement? is there some kind of screen where i can >> query and update the existing data model manually and translate the data >> into the new model or do i have to do it in the application code. >> >> -- >> You want it fast, cheap, or right. Pick two!! >> >> -- >> 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. >> > -- --Guido van Rossum (python.org/~guido) -- 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.
