I started allocating negative numbers as ids to my entities(these would be
part of the key) and it seems to work.
The appengine returns results sorted in the ascending order of keys and
hence if I provide keys as -8, -9, -10 etc., I would get the results as -10,
-9, -8 and so on which suffices my
Hey Nischal,
You could insert some records with known key names in various
orders and a common value for a property to query on. If the results
come back out key-ordered, that would be a good indication that the
method might work. Also, I *think* there are some videos, groups
posts, and refere
@Robert Thank you so much! Any idea how I can confirm on the timestamp + key
thingy? I always need it based on timestamp (descending). If that works then
it would help me a lot!
I have looked into exploding indexes. My query would always be equality
checks over list properties exclusively. I'm hop
You probably need to be aware of exploding indexes if you're indexing
a list property. It is just something you should consider and be
aware of.
http://code.google.com/appengine/docs/python/datastore/queries.html#Big_Entities_and_Exploding_Indexes
If you're always planning to sort by timestamp
We're building a new web product.
1. We have the concept of *label* in them.
2. Each *post* gets one or more *label*.
3. The *posts* have to be displayed sorted according to timestamp in
descending order
We're making use of List (ListProperty) to save these *labels* for
each *post*. It's w
