On Tue, Sep 25, 2012 at 1:12 AM, Moises Belchin moisesbelc...@gmail.com wrote:
Hi Guido,
Thanks for your comments and help.
I think adding sort order by key is a problem. For example:
If you have a kind on which you have equals filters using fetch with limit,
offset you don't need to use
Hi Moises,
I think you may be able to solve this by adding a sort order by key, as follows:
q_next = q.order(MaqHistMov.idsm, MaqHistMov.key)
q_previous = q.order(-MaqHistMov.idsm, -MaqHistMov.key)
FWIW, here is an example that I think represents what you are doing:
class M(ndb.Model):
FWIW, this behavior appears to be a bug in NDB. I've filed
http://code.google.com/p/appengine-ndb-experiment/issues/detail?id=210
I'll investigate.
On Wed, Sep 19, 2012 at 4:22 PM, Guido van Rossum gu...@google.com wrote:
On Wednesday, September 19, 2012 8:51:48 AM UTC-7, Moises Belchin wrote:
Hi Guido,
Thanks for your answer.
We test to use query cursors and we decide don't use them because query
cursors don't work in reverse order if you don't do query orders.
We have queries with many filters and we can't do query orders for this
queries. In this case if we use cursors, the
On Thu, Sep 20, 2012 at 1:59 AM, Moises Belchin moisesbelc...@gmail.com wrote:
Hi Guido,
Thanks for your answer.
We test to use query cursors and we decide don't use them because query
cursors don't work in reverse order if you don't do query orders.
If you have inequalities the order you
On Wednesday, September 19, 2012 8:51:48 AM UTC-7, Moises Belchin wrote:
Hi guys,
I have this query:
q = MyKind.query()
regs = q.fetch(offset = 990, limit = 10) // *Returns 10 entities.*
If I press next button on my UI:
q = MyKind.query()
regs = q.fetch(offset = 1000, limit = 10) //
