This library should support the MultiQuery class (docs, source) found in the original datastore API.
Background
According to the App Engine migration guide, the original API is being phased out and developers are being asked to port their code to the GCL libraries. Unfortunately, these newer libraries are missing some of the features found in the older libraries.
The older datastore API supported the class google.appengine.api.datastore.MultiQuery. This class could run multiple queries at once and then merge sort the results in memory. There were plenty of limitations with the MultiQuery class, including large result sets and cursors. However, there are several main advantages:
- Supporting
MultiQuery will ease transition from the old API to the new one
- It is a helpful tool for quickly being able to perform many queries at once.
- It can assist middleware developers when implementing database
IN operators.
Accordingly, I propose a similar class be built for the new datastore libraries.
If MultiQuery is not supported, some migration solution should be outlined in the migration guide.
This library should support the
MultiQueryclass (docs, source) found in the original datastore API.Background
According to the App Engine migration guide, the original API is being phased out and developers are being asked to port their code to the GCL libraries. Unfortunately, these newer libraries are missing some of the features found in the older libraries.
The older datastore API supported the class
google.appengine.api.datastore.MultiQuery. This class could run multiple queries at once and then merge sort the results in memory. There were plenty of limitations with theMultiQueryclass, including large result sets and cursors. However, there are several main advantages:MultiQuerywill ease transition from the old API to the new oneINoperators.Accordingly, I propose a similar class be built for the new datastore libraries.
If
MultiQueryis not supported, some migration solution should be outlined in the migration guide.