# Large list order Go client

**URL:** <https://discuss.aerospike.com/t/large-list-order-go-client/2772>\
**Category:** Go Client\
**Tags:** go, ldt\
**Created:** [April 4, 2016, 11:56pm UTC](https://discuss.aerospike.com/t/large-list-order-go-client/2772 "2016-04-04T23:56:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lime008](https://avatars.discourse-cdn.com/v4/letter/l/7993a0/32.png) [@lime008](https://discuss.aerospike.com/u/lime008)\
**Post date:** [April 4, 2016, 11:56pm UTC](https://discuss.aerospike.com/t/large-list-order-go-client/2772/1 "2016-04-04T23:56:33Z")

</div>

Hi, In a large ordered list I can implement the paging with FindFirst method and then get more items by calling FindFrom with the last item from the previous list of items. So I was wondering, if I use a timestamp to order the items, how could I page the results the other way around? Like first getting the last n items and then calling the FindFrom with a negative count or just order the whole list in a descending order to use the first method.

---

<div class="post-metadata">

**Author:** ![lime008](https://avatars.discourse-cdn.com/v4/letter/l/7993a0/32.png) [@lime008](https://discuss.aerospike.com/u/lime008)\
**Post date:** [April 5, 2016, 12:49am UTC](https://discuss.aerospike.com/t/large-list-order-go-client/2772/2 "2016-04-05T00:49:43Z")

</div>

I think I found a way to do this by my self by turning the timestamp int into a negative value so the order is now inversed.