The Python and Java runtime environments provide several ways to formulate queries. They all do the same thing: they ask the datastore to return the entities (or keys for entities) whose keys and properties meet the given filter criteria, returned in an order determined by sorting the given properties.
One way to formulate a query is with GQL. GQL is a text-based query language that is intended to resemble SQL, the query language of relational databases. It supports only the features of the datastore’s query engine, and therefore lacks many features common to SQL. But it is expressive and concise enough to be useful for datastore queries.
Say we have entities of the kind
representing players in an online role-playing game. The following GQL
query retrieves all
Player entities whose “level”
property is an integer between 5 and 20, sorted by level in ascending
order, then by score in descending order:
SELECT * FROM Player WHERE level > 5 AND level < 20 ORDER BY level ASC, score DESC
You can use GQL to browse the contents of the datastore of your live application using the Administration Console. To do this, select Data Viewer from the sidebar. You can browse entities by kind, or enter a GQL query. You can also create new entities through the Console, though new entities are limited to the kinds, properties, and value types of existing entities. You can also edit the properties of an entity by clicking on its ID. Figure 5-1 shows the results of running a GQL query in the Console. ...