Sign up to access "Laravel Cursor Pagination" right now.

factory to generate these out and the created updates are pretty much, yeah, all the same, obviously apart from the ones that we created, which I'm going to go ahead and delete. So what I'm actually going to do is just go for 15 records. I think that'll be enough. And I'm going to go ahead and manually update the created update for each of these. We could have

done that with our factory with some kind of sequence, but if we just go through and say this one was posted now and then this one was posted afterwards, that gives us a much better order because remember over in our post index controller, we're using latest, which orders by the creator that day. So I'm going to go through and update all of these so they're in a much better

sequential order and we'll come back to our page to have a look. Okay, so I've gone ahead and updated all of these. So these are now in a sequential created out order. And if we come over now, you can see we've got 15, 14, 13, 12, all the way down to six, and then we should see five. So this actually gives us a much better understanding of how this is working. If we hit

post on this and we post something new, the next one we should see when we load more is five. Obviously we don't. We see six because that's been offset by one by that post we've created. Same if we were to do this twice, that would be offset by two. So pretty much what we looked at in the last part, but just slightly different. So you can see here that we've got eight and seven again because

that's an offset of two and then six, five, four, three. So if we come over to our post endpoint here, we're going to very easily switch this over to cursor pagination. So to do this, instead of the paginate method, we use the cursor paginate method. Now with this, we're not going to get as much information because of the way cursor pagination works behind the scenes. It just

does not, it cannot give us as much information. And if we give this a refresh, you'll see here that we're missing quite a bit here. So we know how many are per page. That's pretty obvious. But with cursor pagination, we don't know the last page URL and any of the other information. So really what we just have is a next page URL, which to be honest, considering this will

eventually become null, is enough for us to implement what we need. In fact, we don't need to change anything about the implementation that we've created over on app.view because we use the next page URL here to give us that value that we make another request to. So let's try this out. I'm going to go ahead and hit load more. And sure enough, it works exactly the same way. Now at the

moment, this button will continue to make requests. So if we just check out our network tab here, this will still continue to make requests. Let's just go down and try this out. And it will actually break, yeah, because we are making a request to null technically here. So we can very, very easily fix that in just a moment. The point is now that now we have cursor pagination set up. And if we

come over to the database here and delete these just to test this out, when we make a request and add a new item to the stack and we hit load more, you can see it loads in exactly the same place because this sets the position which we want to load from. And that won't change when we add things to our database table. So although that was a long way of getting around to show you a very

simple method change over here, hopefully now that makes a little bit more sense. Cursor pagination is pretty complicated. You can go ahead and read up on it a little bit more to find out more about it. It's very SQL heavy, but this should have given you a really good idea as to when cursor pagination can be really helpful. Now finally, let's just fix this load more button issue up

because at the moment, we don't really want to show this if the next page URL is null. So a very simple if statement on here just to check that that's not null. And if we come over and give this a refresh and we hit load more, that disappears because the next page URL in our API endpoint will have turned to null.