Hi Oliver,
Doing a get() for a specific key is definitely much faster than doing
a query, even if that query only returns one entity. As an example,
take a look at the System Status page for gets:
Hi Jason,
On May 12, 5:12 pm, Jason (Google) apija...@google.com wrote:
[...] thereby improving the performance of your application [...]
What is the extent of this? I suppose you mean that if you know the
key, you can construct an object and save it to datastore by
overwriting it, without
Yes. See the Model functions that are available:
http://code.google.com/appengine/docs/python/datastore/modelclass.html#Model_get_by_key_name
http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/datastore/DatastoreService.html
- Jason
On Wed, May 13, 2009 at 4:47 AM, Big
When you create entities, you have the option of specifying a unique key
name that you can use to reference these entities directly (e.g. retrieving
entities without queries, thereby improving the performance of your
application).
I'm not sure what you mean by this. Are you saying if I know
On Wed, May 13, 2009 at 12:47 PM, Big Stu stu.dohe...@gmail.com wrote:
When you create entities, you have the option of specifying a unique key
name that you can use to reference these entities directly (e.g. retrieving
entities without queries, thereby improving the performance of your
On May 12, 11:58 am, Oliver Zheng goo...@oliverzheng.com wrote:
I have been looking at the stored data of some apps, and noticed those
3 columns. Key appears to be a hash/string of some sort. ID is usually
empty. Key name looks like an actual readable identifier, but it's
usually just key_
Hi Oliver. This page may help explain the difference between these fields:
http://code.google.com/appengine/docs/python/datastore/keysandentitygroups.html
When you create entities, you have the option of specifying a unique key
name that you can use to reference these entities directly (e.g.
