perhaps your question could be 'how can i do xyz given the 1000 result limit?'
basically can your task be done some other way? perhaps you can
calculate something at write time. eg if its a sum or count you want.
the limitations sometimes requires thinking outside the box!
On 19/04/2009, Chris
CHeck this:
http://google-appengine.googlegroups.com/web/efficient_paging_using_key_instead_of_a_dedicated_unique_property.txt?gda=7FbhWXcAAACSStSWrftt07H4FK2Rtvurv5Qi9dmYyYZMEnTZCjCsYQQgER4RQV57mxjvIzAWBZmQ3TeCdbqm30Qz_AwgYlIpRbcWRj3jGGBm-fgbnPJIYc4-hXRRmo3Xgj6KgtSLBeZ45alvcyXc30EbEX-RNDZveV4duv6
Thanks, but I don't see how that's relevant. Like I said, the ordering
of an object's key has no correlation to an object's date.
I'm not trying to simply page. That's trivial using the method listed
in your link. What I'm trying to do is page through a set of objects
limited by a date range.
Ch
Hi Chris,
You can do this by adding an extra attribute to the object that
contains the date and a sequence number.
The extra attribute is an IntegerProperty. It has arbitrary precision,
unlimited bit length.
If you store (long(datetime.toordinal(myRecord.date))<<128)+long(sequenceNum)
you can s
Thanks, that's a good thought. I agree that it should be done in a
transaction. However, I don't believe App Engine allows you to run
queries in a transaction.
Chris
2009/4/20 djidjadji :
>
> Hi Chris,
>
> You can do this by adding an extra attribute to the object that
> contains the date and a
You can use a unique counter for all the entities. 2**128 is a lot.
You can use a sharded counter to generate the unique id's, it uses a
transaction.
2009/4/20 Chris Spencer :
>
> Thanks, that's a good thought. I agree that it should be done in a
> transaction. However, I don't believe App Engine