nicolaibaaring
nicolaibaaring
FFilament
Created by nicolaibaaring on 11/18/2024 in #❓┊help
Eloquent query using integers not working in Filament context
Just as an additional note, this is using MySQL and the database strict setting does not change anything. The problem is only found when using integers and when the query is running in a Filament context.
4 replies
FFilament
Created by nicolaibaaring on 11/18/2024 in #❓┊help
Eloquent query using integers not working in Filament context
A simple builder dd() gives this:
"
select * from `tasks` where `project_id` = ? and (`status` in (?, ?, ?, ?) or (`status` = ? and `created_by` = ?)) and `tasks`.`deleted_at` is null

" // vendor\laravel\framework\src\Illuminate\Database\Query\Builder.php:4406
array:7 [▼ // vendor\laravel\framework\src\Illuminate\Database\Query\Builder.php:4406
0 => 287885550034231034
1 => 2
2 => 4
3 => 8
4 => 9
5 => 0
6 => 287885378390727198
]
"
select * from `tasks` where `project_id` = ? and (`status` in (?, ?, ?, ?) or (`status` = ? and `created_by` = ?)) and `tasks`.`deleted_at` is null

" // vendor\laravel\framework\src\Illuminate\Database\Query\Builder.php:4406
array:7 [▼ // vendor\laravel\framework\src\Illuminate\Database\Query\Builder.php:4406
0 => 287885550034231034
1 => 2
2 => 4
3 => 8
4 => 9
5 => 0
6 => 287885378390727198
]
So these are all integers. In this case, the table query works, and gives the right results, but clicking a row to open the modal (this is a simple resource) does not open the modal (same as ModelNotFound). I might have mentioned it wrong above, because the missing models in the table vs the infolist/form depends on which params are cast to string. If I add a method to my custom query builder that converts all numeric params to string, then both the table and the infolist/form works as intended.
4 replies
FFilament
Created by nicolaibaaring on 6/11/2024 in #❓┊help
Query string on simple resource modals
3 replies