Just found your channel Dan, keep up the great work! Consider using lombok to cut back on all the boiler plate code. It's easy to generate with the IDE, but I find it a bit tedious and distracting to watch. It even would have avoided that issue where you needed to regen the constructor because a field was added.
Great video Dan! A bit unrelated, but maybe you could also do in the future a video about async methods in Spring (configuring the pool; any possible differences between Spring Boot 2 and 3 regarding this topic; exception handling strategies etc.)
This was so useful! Do you have any pointers on how one could extend this to allow the client to define a custom sorting (and also filtering)? I know that GraphQL doesn't have a spec for any of these, and I'm just learning about Spring, so I'm curious on what could be a good way to approach this
It makes absolutely no sense how spring implemented cursor because JPA still uses offset while executing query. The most important thing is that cursor is a powerful performance optimizer because the main idea is to use PK in conditions like `where ID > cursor` query uses PK and then works as offset.. this solution is several times faster than offset. What they did is just a cover for normal pagination. IT'S SUCK!!
Could you deep dive some more into this, covering things like how to get counts into the response, such as page count and total count ect.
Just found your channel Dan, keep up the great work! Consider using lombok to cut back on all the boiler plate code. It's easy to generate with the IDE, but I find it a bit tedious and distracting to watch. It even would have avoided that issue where you needed to regen the constructor because a field was added.
Great video Dan!
A bit unrelated, but maybe you could also do in the future a video about async methods in Spring (configuring the pool; any possible differences between Spring Boot 2 and 3 regarding this topic; exception handling strategies etc.)
Nossa brabo demais. O caba é bom.
Hey, is there a way to specify additional field next to edges and and pageInfo, e.g. totalCountOfElements?
This was so useful!
Do you have any pointers on how one could extend this to allow the client to define a custom sorting (and also filtering)? I know that GraphQL doesn't have a spec for any of these, and I'm just learning about Spring, so I'm curious on what could be a good way to approach this
It makes absolutely no sense how spring implemented cursor because JPA still uses offset while executing query. The most important thing is that cursor is a powerful performance optimizer because the main idea is to use PK in conditions like `where ID > cursor` query uses PK and then works as offset.. this solution is several times faster than offset. What they did is just a cover for normal pagination. IT'S SUCK!!