From 5e3c22ea5e8d6a534437df87bca9a677c2a8e4ad Mon Sep 17 00:00:00 2001 From: M41den <38406005+m41denx@users.noreply.github.com> Date: Tue, 28 Oct 2025 15:48:35 +0300 Subject: [PATCH] Fix weird postgres behavior when selecting mounts (#1842) Co-authored-by: Boy132 --- app/Filament/Admin/Resources/Mounts/MountResource.php | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/app/Filament/Admin/Resources/Mounts/MountResource.php b/app/Filament/Admin/Resources/Mounts/MountResource.php index d46a94799..4e8178a13 100644 --- a/app/Filament/Admin/Resources/Mounts/MountResource.php +++ b/app/Filament/Admin/Resources/Mounts/MountResource.php @@ -162,7 +162,8 @@ class MountResource extends Resource Section::make()->schema([ Select::make('eggs')->multiple() ->label(trans('admin/mount.eggs')) - ->relationship('eggs', 'name') + // Selecting only non-json fields to prevent Postgres from choking on DISTINCT JSON columns + ->relationship('eggs', 'name', fn (Builder $query) => $query->select(['eggs.id', 'eggs.name'])) ->preload(), Select::make('nodes')->multiple() ->label(trans('admin/mount.nodes'))