Lisk-sdk: Inconsistent response for /transactions endpoint

Created on 16 Apr 2018  路  2Comments  路  Source: LiskHQ/lisk-sdk

Expected behavior

Given I make the following calls:

/transactions?blockId=:blockId&sort=timestamp:desc&offset=0&limit=51 and
/transactions?blockId=:blockId&sort=timestamp:desc&offset=50&limit=51

I expect the last item returned by the first call to be the same as the first item returned by the second call.

Actual behavior

It is not.

Steps to reproduce

Using the following test database:

Compare the first call with the second call

Which version(s) does this affect? (Environment, OS, etc...)

v1.0.0-beta.5

improvement framewormoduletoken

Most helpful comment

Maybe it's a good idea to introduce this second default sort for all endpoints that have sorting option.

All 2 comments

Your calls are getting transactions with timestamp 0. What we need is a second default sort parameter as a tiebreaker.

Maybe it's a good idea to introduce this second default sort for all endpoints that have sorting option.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Nazgolze picture Nazgolze  路  3Comments

toschdev picture toschdev  路  3Comments

ScrewchMcMuffin picture ScrewchMcMuffin  路  3Comments

karek314 picture karek314  路  3Comments

diego-G picture diego-G  路  3Comments