Using this query: bills(func: has(billsType), orderdesc: date, offset: 5, first: 5) { expand(_all_) } Everything works as expected (I get result 5 to 10). But when I have: bills(func: has(billsType), orderdesc: date, orderdesc: time, offset: 5, first: 5) { expand(_all_) } I get the same res…

One rule for sorting is to have any value indexed. If not so, Dgraph will ignore them. Add any dummy date to the other nodes.

Hey Michel, thanks for replying! Both ‘date’ and ‘time’ values are indexed. Offset works fine if I use only one or the other for ordering, but not when I use both. It really seems to be the combination of using both that causes the issue. What’s more, the ordering is fine; the bills are ordered fi…

The idea of pagination is simple. If you have 10 nodes and use “offset: 0, first: 5” you will have two pages. Because the pagination will divide 10 nodes by 5. If you use “offset: 5*, first: 5” you will be on the second page. And if you use “offset: 10*, first: 5” will not return anything, for the…

Hey there Michel! I think you haven’t understood. First of all, what you say is inaccurate. Using “offset: 1, first: 5” will show me results 2-6 as opposed to 1-5. To display the second page I would use “offset: 5, first: 5”. The problem is that offset doesn’t work when using multiple order statem…

[image] Awoogamuffin: First of all, what you say is inaccurate. Using “offset: 1, first: 5” will show me results 2-6 as opposed to 1-5. To display the second page I would use “offset: 5, first: 5”. You’re right. I confused myself. In fact we have to do the division and use the multiples manua…

Hi Michel, [image] MichelDiz: Need to check if the issues would be related to datetime only. I guess is the case I don’t thing that it is related only with datetime. I have similar problem with string predicates.

Selmeci is right. I’ve just run the same test using strings rather than datetime. You can try yourself, using this data: { "set": [ { "string1": "A", "string2": "A", "num": 1 }, { "string1": "A", "string2": "B", "num": 2 }, { "string1": "…

I guess if the strings have the right order will be okay tho. Your example confuses Dgraph’s sorting. Page 1 { fun(func: has(num), orderasc: string1, orderasc: string2, first: 5, offset: 0) { expand(_all_) } } Result { "data": { "fun": [ { "num": 1, "string1"…

The data you’ve used makes the second order command redundant. The second order command only comes into play when the first order command returns an equal result. You would need several entries that have equal values for “string1” for the second order command to be used. If you use the data example…

[image] Awoogamuffin: The data you’ve used makes the second order command redundant. I made like this to show how it behaves. I did a continuous ordering via two different predicates. That way I’m pretty sure Dgraph is applying the two parameters correctly. By my tests everything is normal. …

Offset appears not to work with multiple order statements

Users

selmeci May 3, 2019, 7:22am 13

I can confirm that the problem is related to offset. I have a similar problem on my data sample.

Topic		Replies	Views
Pagination - Query language Documentation	0	441	August 28, 2020
After and orderdesc: question on large datasets, ordering, and pagination Dgraph kind:question , dql	2	230	March 26, 2024
Pagination using "after" doens't respect sort order Dgraph dgraph , status:accepted , kind:bug , area:querylang:pagin	5	703	November 25, 2019
Order and Pagination - Graphql Documentation	1	716	February 24, 2021
Why are date filtered out from results when using sorting? Dgraph	6	835	February 7, 2019

Offset appears not to work with multiple order statements

Related topics