An AsyncDatastoreService implementation that is pinned to a specific appId and namesapce. This
implementation ignores the "current" appId provided by
ApiProxy.getCurrentEnvironment().getAppId() and the "current" namespace provided by
NamespaceManager.get(). Note, this is particularly important in the following methods:
Returns the current transaction for this thread, or throws an exception if there is no current
transaction. The current transaction is defined as the result of the most recent, same-thread
invocation of beginTransaction() that has not been committed or rolled back.
Use this method for when you expect there to be a current transaction and consider it an
error if there isn't.
Returns the current transaction for this thread, or returns the parameter if there is no
current transaction. You can use null or provide your own object to represent null. See
#getCurrentTransaction() for a definition of "current transaction."
Use this method when you're not sure if there is a current transaction.
This method returns a PreparedQuery which can be used to execute and retrieve
results from the datastore for query.
This operation will not execute in a transaction even if there is a current transaction and
the provided query is an ancestor query. This operation also ignores the ImplicitTransactionManagementPolicy. If you are preparing an ancestory query and you want it
to execute in a transaction, use #prepare(Transaction, Query).
Exhibits the same behavior as #prepare(Query), but executes within the provided
transaction. It is up to the caller to commit or rollback. Transaction can be null.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["AdminDatastoreService is an implementation of AsyncDatastoreService that operates within a specified appId and namespace, ignoring the current global settings."],["This class provides methods for creating Query, Entity, and Key objects that are also bound to the same appId and namespace."],["It provides several methods such as `getIndexes()`, `getDatastoreAttributes()`, and `allocateIds()` which are all affected by the pinned appId and namespace."],["Static `getInstance()` methods are used to get instances of AdminDatastoreService for specific appIds and namespaces, and can also be created with a configuration."],["Direct access to this class by users is discouraged."]]],[]]
