How to change path and query string when using LengthAwarePaginator?

@tykus thanks, going to try now. I think the docs on Pagination are too concise

@Ligonsker there is plenty of source-diving material at https://laravel.com/api/9.x/Illuminate/Pagination/AbstractPaginator.html

@tykus thanks, will go to the source more instead of just the docs

Also, the methods setPath and setPageName worked. However, the links don't work anymore: The show up, and also the url changes to what I set, but the page itself doesn't change, it remains on page 1. this is how I used it:

$paginator = new LengthAwarePaginator();
$paginator->setPath('myPath');
$paginator->setPageName('pageName');

@Ligonsker and you manually set the items in the Paginator also?

@tykus yes but I think the problem is somewhere here:

$page = $page ?: (Paginator::resolveCurrentPage() ?: 1);
$items = $items instanceof Collection ? $items : Collection::make($items);
return new LengthAwarePaginator($items->forPage($page, $perPage), $items->count(), $perPage, $page, $options);

maybe the original way of using $page ?: (Paginator::resolveCurrentPage() ?: 1); doesn't work anymore because I changed the name and now there is an issue with resolveCurrentPage?

Update: I just realized that even though the links are showing my custom query string, it only works if I use the old query string with the value page (If I change in the url to ?page=2 it will go to the correct page)

@Ligonsker if you are not using the standard page parma, then you need to pass the custom page name to the resolver, e.g.

Paginator::resolveCurrentPage('pageName')

@tykus thank you! you are correct and it's working now

@Tray2 It's a complex query I could not find a way to translate to Query Builder/Eloquent: https://laracasts.com/discuss/channels/code-review/is-it-possible-to-use-the-following-query-without-raw-sql

so I had to convert the array returned by DB::select to a custom paginator :/

@Ligonsker then I suggest moving the query into a database view and then query it like a regular table.

@Tray2 I never used views before, and it needs to be ready soon. But I am going to read about that. With view I basically store the complex query, give it some name and then I can query it with something like regular select? Or it acts as a table name?

@Ligonsker They are like read only tables, so all you need to do is create one, a model for it and then you can use it.

Here you can read a bit about it

https://tray2.se/posts/database-design-part-2

@Tray2 I did not read all the article yet, but can you help me get the idea:

Let's say I have the Messages table with all the information. And I need some specific data from the Messages table. In my case - the oldest messages from each user. I'll create a view called OldestMessageFromEachUser, and what it does is to run the complex query that I want from the Messages table and "clone" the result from Messages table to the OldestMessageFromEachUser view table, and every time Messages updates, so will OldestMessageFromEachUser, and I can read from it?

@Ligonsker Yeah kinda, the view is a query that exists in the database as a view and you make your queries agains that query.

You could say that it's similar to an inline view, but the code is stored in the database.

SELECT t1.id
FROM (SELECT id FROM table1) AS t1

@Tray2 haha I don't even know what an inline view is, my DB knowledge is not that broad, I gotta read that article :}

@Ligonsker an inline view is a sub query in the from part of the query.

@Tray2 thank you, got it! I read about it also in your article, here is the example:

SELECT t.*
FROM (SELECT id, title, created_at, 'books' source
      FROM books
      UNION ALL
      SELECT id, title, created_at, 'movies'
      FROM movies
      UNION ALL
     SELECT id, title, created_at, 'records'
     FROM records) t
ORDER BY t.created_at DESC
LIMIT 10;

@Ligonsker Exatly, that is a pretty nice example of both using an inline view and using a union to get data from three different tables at once, so that you can list the latest 10 rows.