Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pagination question #238

Closed
yury opened this issue Sep 25, 2017 · 3 comments
Closed

Pagination question #238

yury opened this issue Sep 25, 2017 · 3 comments

Comments

@yury
Copy link

yury commented Sep 25, 2017

Turns out that traditional paging sometimes is better (if you want to show all pages).

I tried to to implemented with join-monster and stuck.

  1. I tried to append LIMIT and OFFSET to generated SQL and it worked. But I can't find a place where I can inject count(*) OVER() AS total.
  2. I tried to query with knex in resolver, but can't find a good way to map queryAST to select sql fields.

Any help would be great.

@amosyuen
Copy link

@yury did you ever figure this out?

@acarl005
Copy link
Collaborator

acarl005 commented Jul 4, 2018

Can you clarify what you mean by "traditional paging"? Using LIMIT and OFFSET is an option provided by JM (docs)

@nicoabie
Copy link
Contributor

Closing as there was no answer in 6 years

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants