query override
ChatGPT just told me to override Filament's query method (see photo)
This is because I would have to traverse models. Payment belongs to a client, which belongs to a contract, which belongs to a client, which belongs to a user. I was going to make an accessor like $this->contract->client->user->name but then I'd have an n+1 problem, right?
So is this query override standard practice? How should this be handled in V3?
This is because I would have to traverse models. Payment belongs to a client, which belongs to a contract, which belongs to a client, which belongs to a user. I was going to make an accessor like $this->contract->client->user->name but then I'd have an n+1 problem, right?
So is this query override standard practice? How should this be handled in V3?
Solution
So. TextColumn::make(‘blah.name’) will display the name attribute on the blah relationship.
