Best Approach for Service History Search: Dynamic Data or New Table?
Hi everyone!
I’m building a vehicle workshop/garage application using Laravel + Filament and have the following resources set up:
CustomerResource
VehicleResource
InvoiceResource
QuotationResource
RentalResource
I want to add a Service History feature where users can search for a vehicle’s service history by Plate Number, VIN, or Customer Name etc.
My question is:
Should I create a ServiceHistory model and table to store the search results, or is it better to just pull data dynamically from existing resources (like InvoiceResource and VehicleResource) without creating a new model?
Would pulling data dynamically be efficient, or should I create a new table for scalability?
I’d appreciate any advice or suggestions on the best approach!
Thanks!
1 Reply
thanks for your reply @Minima Takashi
Hello Minima,
Yes please!