transactionsByOwner graphql query doesn't work properly when providing last

[mpoplavkov]

The following request works for me:

query Transactions($address: Address) {
  transactionsByOwner(owner: $address, first:10) {
    nodes {
      id
    }
  }
}

Although, if I want to change the ordering and get latest transactions first and therefore provide last parameter instead of first, the query returns an empty response:

query Transactions($address: Address) {
  transactionsByOwner(owner: $address, last:10) {
    nodes {
      id
    }
  }
}

The account I test on is 0xfe1177573a47310756f27ef25c7229b5da8d5109a7258b297f23a6768c78cb40.

Expected: when providing last, the query should return a nonempty result, similar to the case with first, but with a different ordering.

[xgreenx]

Thank you for reporting it=) I guess, you got the weird response during interaction with beta 2.

We already added some handling for it in beta 3. After the change we don't allow backward queries because underlying database doesn't support it too. So with the new version, you should get an error like "reverse pagination isn't supported for this resource".

While our main database is the RocksDB, we don't plan to support functionality that is not supported by this database. But we have an issue to move all GraphQL stuff to the fuel-indexer.

After resolving this issue, we will support queries like this and more=)

I will close this issue for now, because it will be related to the indexer in the future