Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I had this silly idea to create a report builder (well, not exactly a “builder”) where as there’s a table called “query” which holds raw mysql query. Within that query are column-able fields such as “start date” or “person name” (it depends on the report). And there’s another table related to the report table which holds the fields and their types so we can show them on the SPA/ frontend so the users can apply these filters.
Then again, how can I display a field like “users list drop down” where the users list is loaded from the server.
This is what I have so far. The basic idea is to allow the super users to write query and give it to the users without creating separate frontend to get the specific type of report with pre-defined fields on them. Instead, do it all in one template. What can I do to improve this idea? Any suggestions?
An example report I generate:
However the input form is designed to "drill down" for more detail. For example if you need to see just utilities over a given period of time.
There is also an option to view a paginated report of all transactions of a given period, with double pagination, i.e., a next category link, and under that a paginated list.
But for an admin, you could create a similar input form that encompasses various searches and drill down levels.
Take a look at this. It is made for something like that, but uses eloquent instead of raw sql https://spatie.be/docs/laravel-query-builder/v5/introduction
Please or to participate in this conversation.