After updating Prisma from `2.0.0-beta.6` to `2.1....
# orm-help
m
After updating Prisma from
2.0.0-beta.6
to
2.1.3
my "skip" properties are gone and this broke some of our queries. Is there a way of having it back? I'm using a calculation of the current page + the amount of items in the page to find the correct amount to skip, without the need of waiting for a network request to do something like, get the id and filter only the ones after it etc. (I'm using @nexus/schema and nexus-prisma but those were unchanged)
r
Hey Matheus 👋 You would need to update the way pagination works as the API had changed here.
m
Hi Ryan! Thanks for the quick answer, you guys are awesome! But it seems that the skip argument is still in there, what happened with me is that it disappeared entirely from my queries. Maybe it's a nexus-prisma issue then? I didn't change anything in nexus-prisma, but even after updating it I'm still not getting the skip property. But thank you for sending me that link! I'll keep using it to check the changes between updates.
r
Could you share where it has disappeared from? Also did you perform a
prisma generate
after updating Prisma?
m
Hey sorry I was assigned to a different task for now. But I shared a print of the diff on where it disappeared(graphql schema) in the original message, and yes i did run generate.
r
Could you try updating
nexus-prisma
as well and check?
m
I did! Same thing
r
I guess it's due to the strategy not exposed by Nexus as described here. You would need to resort to cursor pagination for the timebeing.
m
I see. That's unfortunate. Thank you for finding the issue. There are so many nexus repos currently that I get lost.
💯 1
😅 1
I just found out that to have the
skip
property I just had to add
paginationStrategy: 'prisma'
to my `nexusSchemaPrisma`configuration. It will then mirror prisma's pagination of skip and take instead of relay's after
👍 1
💯 1