On Wed, Dec 9, 2009 at 11:44 AM, Manuel <[email protected]> wrote: > On Dec 9, 7:11 am, jd <[email protected]> wrote: > > Hi Manuel, I believe that in a single property index, entries with the > > same value are sorted by key, therefore the results of a merge join > > will always be in key order. If you can ensure that your tag entities > > have keys in chronological order then this should be possible. I am > > not certain but I think that auto generated ids (as opposed to key > > names) are not guaranteed to be in order so you would probably need to > > set the key name yourself from a counter. Perhaps you could use > > memcaches increment method here? > > > > John > > Thanks John, I'll try this. > > I wonder if anyone from Google could confirm that entries with the > same index value are sorted by key? >
Correct. Every query has an implicit final sort by key. -Nick Johnson > > Thanks, > Manuel > > -- > > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
