google.appengine.ext.gql package


GQL -- the SQL-like interface to the datastore.

Defines the GQL-based query class, which is a query mechanism for the datastore which provides an alternative model for interacting with data stored.


google.appengine.ext.gql.Execute(query_string, *args, **keyword_args)source

Execute command to parse and run the query.

Calls the query parser code to build a proto-query which is an unbound query. The proto-query is then bound into a real query and executed.

  • query_string -- properly formatted GQL query string.

  • args -- rest of the positional arguments used to bind numeric references in the query.

  • keyword_args -- dictionary-based arguments (for named parameters).


the result of running the query with *args.

class google.appengine.ext.gql.GQL(query_string, _app=None, _auth_domain=None, namespace=None)source

Bases: object

A GQL interface to the datastore.

GQL is a SQL-like language which supports more object-like semantics in a language that is familiar to SQL users. The language supported by GQL will change over time, but will start off with fairly simple semantics.

  • reserved words are case insensitive

  • names are case sensitive

The syntax for SELECT is fairly straightforward:

SELECT [[DISTINCT] <property> [, <property> ...] | * | __key__ ]

[FROM <entity>] [WHERE <condition> [AND <condition> ...]] [ORDER BY <property> [ASC | DESC] [, <property> [ASC | DESC] ...]] [LIMIT [<offset>,]<count>] [OFFSET <offset>] [HINT (ORDER_FIRST | FILTER_FIRST | ANCESTOR_FIRST)] [;]

<condition> := <property> {< | <= | > | >= | = | != | IN} <value> <condition> := <property> {< | <= | > | >= | = | != | IN} CAST(<value>) <condition> := <property> IN (<value>, ...) <condition> := ANCESTOR IS <entity or key>

Currently the parser is LL(1) because of the simplicity of the grammer (as it is largely predictive with one token lookahead).

The class is implemented using some basic regular expression tokenization to pull out reserved tokens and then the recursive descent parser will act as a builder for the pre-compiled query. This pre-compiled query is then bound to arguments before executing the query.

Initially, three parameter passing mechanisms are supported when calling Execute():

  • Positional parameters

Execute('SELECT * FROM Story WHERE Author = :1 AND Date > :2') - Named parameters Execute('SELECT * FROM Story WHERE Author = :author AND Date > :date') - Literals (numbers, strings, booleans, and NULL) Execute('SELECT * FROM Story WHERE Author = 'James'')

Users are also given the option of doing type conversions to other datastore types (e.g. db.Email, db.GeoPt). The language provides a conversion function which allows the caller to express conversions of both literals and parameters. The current conversion operators are: - GEOPT(float, float) - USER(str) - KEY(kind, id/name[, kind, id/name...]) - DATETIME(year, month, day, hour, minute, second) - DATETIME('YYYY-MM-DD HH:MM:SS') - DATE(year, month, day) - DATE('YYYY-MM-DD') - TIME(hour, minute, second) - TIME('HH:MM:SS')

We will properly serialize and quote all values.

It should also be noted that there are some caveats to the queries that can be expressed in the syntax. The parser will attempt to make these clear as much as possible, but some of the caveats include:

  • There is no OR operation. In most cases, you should prefer to use IN to express the idea of wanting data matching one of a set of values.

  • You cannot express inequality operators on multiple different properties

  • You can only have one != operator per query (related to the previous rule).

  • The IN and != operators must be used carefully because they can dramatically raise the amount of work done by the datastore. As such, there is a limit on the number of elements you can use in IN statements. This limit is set fairly low. Currently, a max of 30 datastore queries is allowed in a given GQL query. != translates into 2x the number of datastore queries, and IN multiplies by the number of elements in the clause (so having two IN clauses, one with 5 elements, the other with 6 will cause 30 queries to occur).

  • Literals can take the form of basic types or as type-cast literals. On the other hand, literals within lists can currently only take the form of simple types (strings, integers, floats).

SELECT * will return an iterable set of entities; SELECT __key__ will return an iterable set of Keys.

Bind(args, keyword_args, cursor=None, end_cursor=None)source

Bind the existing query to the argument list.

Assumes that the input args are first positional, then a dictionary. So, if the query contains references to :1, :2 and :name, it is assumed that arguments are passed as (:1, :2, dict) where dict contains a mapping [name] -> value.

  • args -- the arguments to bind to the object's unbound references.

  • keyword_args -- dictionary-based arguments (for named parameters).


datastore_errors.BadArgumentError -- when arguments are left unbound (missing from the inputs arguments) or when arguments do not match the expected type.


The bound datastore.Query object. This may take the form of a MultiQuery object if the GQL query will require multiple backend queries to statisfy.

EnumerateQueries(used_args, args, keyword_args)source

Create a list of all multi-query filter combinations required.

To satisfy multi-query requests ("IN" and "!=" filters), multiple queries may be required. This code will enumerate the power-set of all multi-query filters.

  • used_args -- set of used positional parameters (output only variable used in reporting for unused positional args)

  • args -- positional arguments referenced by the proto-query in self. This assumes the input is a tuple (and can also be called with a varargs param).

  • keyword_args -- dict of keyword arguments referenced by the proto-query in self.


A list of maps [(identifier, condition) -> value] of all queries needed to satisfy the GQL query with the given input arguments.

Run(*args, **keyword_args)source

Runs this query.

Similar to datastore.Query.Run. Assumes that limit == -1 or > 0

  • args -- arguments used to bind to references in the compiled query object.

  • keyword_args -- dictionary-based arguments (for named parameters).


A list of results if a query count limit was passed. A result iterator if no limit was given.

TOKENIZE_REGEX = <_sre.SRE_Pattern object at 0x3da4fb0>

Return the compiled list of filters.


Return the datastore hint.


Returns True if this query is marked as distinct.


Returns True if this query returns Keys, False if it returns Entities.


Return numerical result count limit.


Return numerical result offset.


Return the result ordering list.


Returns the tuple of properties in the projection, or None.

class google.appengine.ext.gql.Literal(value)source

Bases: object

Class for representing literal values in a way unique from unbound params.

This is a simple wrapper class around basic types and datastore types.


Return the value of the literal.

Send feedback about...

App Engine standard environment for Python