In accordance with the price documents here , the request keys-onlyis free. Thus, it seems that you can save the reading by doing the following (pseudocode):
keys-only
qo = ndb.QueryOptions(keys_only = True) qry = ModelName.query().filter("name" = "Bob") keys = qry.fetch(20, options = qo) #keys-only fetch
Then after that I can get my entities by evaluating 1 reading per entity:
entities = ndb.get_multi(keys)
Why is this considered better than fetching objects (i.e. fetching only for keys)?
Also, where does the request come from? When is it running fetchor when is an object querycreated?
fetch
query
"", 1 . RPC .
(.. ), , . RPC, , , , , , . RPC ( batch_size, RPC-, ).
batch_size
, , - RPC, , , , . , RPC, .
, , , fetch. .
, -: . , , "" , . , , , , , , , , -.
Source: https://habr.com/ru/post/1548558/More articles:Firebase onDisconnect when disconnecting WIFI - firebaseTkinter IntVar returns PY_VAR0 instead of value - pythonCan I create a synonym for the t-sql built-in function? - sql-serverGLSL Shader Error "Конструкторские вызовы могут не иметь точности" - iosIs there a way to show progress on the Github Wiki? - githubWhat is the difference between a console application and a Windows application in .NET at startup - c #How to change a class from jquery, but remove this class from another object - javascriptIn Android, how can I set the value of an edit field in a WebView using Javascript - javascriptGraphic graph of matlab data by image - imageRun emulator using android L - android-5.0-lollipopAll Articles