Hi guys, So yes, Anastasios' solution should be the correct one. Can you confirm if it does work David?
Anastasios, when you go to "Storage -> Cloud Datastore -> Query", you should have a dropdown on "query by kind" which can switch to "Query using GQL". Cheers On Monday, October 12, 2015 at 3:19:24 AM UTC-4, Anastasios Hatzis wrote: > > I wanted to check this out myself, but for some reason I don't have GQL > support in new console of my apps. > > But maybe, the new console uses the *Datastore GQL*, while the old > version used the *Python GQL*. According to the docs there are a few > differences, the ancestor expression is one of them: > > Python GQL expression ANCESTOR IS <entity-or-key-value> is represented in >> Datastore GQL as the more general expression __key__ HAS ANCESTOR >> <key-value> > > > See this section in GQL Reference > <https://cloud.google.com/datastore/docs/apis/gql/gql_reference#unsupported_features_and_behavior_differences_from_mysqlpython_gql> > > I hope this is the reason and I didn't just add more to the confusion > though. And I hope I will get the GQL options too in the Query page. > > > On Monday, October 12, 2015 at 3:07:26 AM UTC+2, Daniel Young wrote: >> >> Sorry for the vagueness - here is my query that still returns the entity >> in the legacy Datastore viewer in the By GQL field >> >> SELECT * FROM Kind where ancestor is key('Kind', 12344567...) >> >> and in the new viewer I get this GQL error >> >> GQL query error >> 'SELECT * FROM Kind where ancestor is key('Kind', 12344567...) LIMIT >> 50': Encountered "ancestor" at line 1, column 32. Was expecting one of: >> <UNQUOTED_NAME> ... <QUOTED_NAME> ... <NAME_BINDING_SITE> ... >> <POSITION_BINDING_SITE> ... <SINGLE_QUOTE_STRING> ... <DOUBLE_QUOTE_STRING> >> ... <INTEGER> ... <DOUBLE> ... "true" ... "false" ... "null" >> >> On Friday, October 9, 2015 at 2:57:02 PM UTC-7, Patrice (Cloud Platform >> Support) wrote: >>> >>> Hi Daniel. >>> >>> What do you mean by "doesn't work"? Is there an error when you run it? >>> or does it run and produces no results? >>> >>> As far as I know GQL didn't change between old and new console, so it >>> should still behave as expected. I'll try to reproduce to see what's >>> happening. In the meantime, if you have an error, including it here would >>> be helpful :). >>> >>> Cheers! >>> >>> On Friday, October 9, 2015 at 12:04:44 PM UTC-4, Daniel Young wrote: >>>> >>>> I found like many others being redirected to the the new datastore. My >>>> trusty GQL ancestor query doesn't seem to work anymore >>>> >>>> select * from <<Kind>> where ancestor is key('Kind', ID) >>>> >>>> Is there a workaround, is this considered a bug? >>>> >>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/55a48ba7-55a2-4773-8597-a242ecd25de6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
