Take a look at these links. It should give you a clue to avoid LIMIT /
OFFSET.
https://www.citusdata.com/blog/2016/03/30/five-ways-to-paginate/
http://use-the-index-luke.com/blog/2013-07/pagination-done-the-postgresql-way
Regards,
Walter
On Sep 29, 2016 19:19, "Guyren Howe" wrote:
>
> On Sep
> On Sep 29, 2016, at 16:14 , Colin Morelli wrote:
>
> Well then...just like that you made me feel like a total idiot! Hah.
>
> I guess that would work fine. I just need to encode some additional
> information in the pagination links that the API returns (a pagination
> "marker" would be a co
Well then...just like that you made me feel like a total idiot! Hah.
I guess that would work fine. I just need to encode some additional
information in the pagination links that the API returns (a pagination
"marker" would be a combination of created_at and uuid).
I know this question is virtuall
On Sep 29, 2016, at 16:03 , Colin Morelli wrote:
>
> Hey list,
>
> I'm using UUID primary keys in my application. I need to add pagination, and
> am trying to avoid OFFSET/LIMIT. I do have a created_at timestamp that I
> could use, but it's possible for multiple records to be created at the sa
Hey list,
I'm using UUID primary keys in my application. I need to add pagination,
and am trying to avoid OFFSET/LIMIT. I do have a created_at timestamp that
I could use, but it's possible for multiple records to be created at the
same timestamp (postgres offers millisecond precision here, I belie
