[PATCH] - Query pagination fails without any filters.

[mizuno@…]

How To Reproduce:

1. Go to Custom Query.
2. Remove any filters and update.
3. Click any page link except page 1.
4. You get same results as page 1 and paging link disappers.

System Information:

• the Operating System: Solaris 10
• the Python version used: 2.5.2
• the database backend and their bindings: sqlite pysqlite3

Cause:

• Query uses a previous result even if the page number changes unless query_constraints (i.e. filters) change.
• With filters, query returns the addition of previous results and filtered results, so pagination works expectedly.
• Without any filters, query returns just the same results as previous. It means the result has as match item as max item per page and paging link disappers.

[osimons]

Testing this on current 0.11-stable (r7546), and I don't see what you're seeing. I don't think the platform makes much difference either, so unless the ticket gets verified by others (or more/other information provided) there won't be any progress.

[Christian Boos]

Isn't that a duplicate of #7544?

[Remy Blank]

Replying to cboos:

Isn't that a duplicate of #7544?

Yes, it is. However, I don't understand the attachment ticket_query.diff​. Does it solve another problem?

[mizuno@…]

Replying to rblank:

Does it solve another problem?

That is exactly a duplicate of #7544 and the attachemnt ticket_query.diff has no intention to solve another problem. I tried to solve this problem by invoking the method query.execute(req, db) insted of query.execute(req, db, orig_list).

[anonymous]

Ok, closing as a duplicate of #7544.