starred/panel
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-02-25 11:20:56 +03:00
Code Issues 42 Packages Projects Releases 12 Wiki Activity

[PR #1842] [MERGED] Fix weird postgres behavior when selecting mounts #1601

New Issue
Closed
opened 2026-02-04 20:00:41 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-04 20:00:41 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/pelican-dev/panel/pull/1842
Author: @m41denx
Created: 10/28/2025
Status: ✅ Merged
Merged: 10/28/2025
Merged by: @notAreYouScared

Base: main ← Head: fix/postgres-mount

📝 Commits (3)

  • 05a4dd2 Fix weird postgres behavior when selecting mounts
  • b18499c I think that was unnecessary
  • 3a86713 Update app/Filament/Admin/Resources/Mounts/MountResource.php

📊 Changes

1 file changed (+2 additions, -1 deletions)

View changed files

📝 app/Filament/Admin/Resources/Mounts/MountResource.php (+2 -1)

📄 Description

Basically I use Pelican with Postgres (I know it's not recommended, but still) and on New Mount page in admin area I get following error:

SQLSTATE[42883]: Undefined function: 7 ERROR: could not identify an equality operator for type json 
LINE 1: select distinct "eggs".* from "eggs" left join "mountables" ... ^ 
(Connection: pgsql, SQL: select distinct "eggs".* from "eggs" left join "mountables" on "eggs"."id" = "mountables"."mountable_id" order by "eggs"."name" asc limit 50) 
(View: /var/www/html/vendor/filament/forms/resources/views/components/select.blade.php) 
(View: /var/www/html/vendor/filament/forms/resources/views/components/select.blade.php) 
(View: /var/www/html/vendor/filament/forms/resources/views/components/select.blade.php) 
(View: /var/www/html/vendor/filament/forms/resources/views/components/select.blade.php) 
(View: /var/www/html/vendor/filament/forms/resources/views/components/select.blade.php)

I'm not sure if this the correct solution, but I opted for selecting only distinct id and name to prevent Postgres from comparing JSON columns

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/pelican-dev/panel/pull/1842 **Author:** [@m41denx](https://github.com/m41denx) **Created:** 10/28/2025 **Status:** ✅ Merged **Merged:** 10/28/2025 **Merged by:** [@notAreYouScared](https://github.com/notAreYouScared) **Base:** `main` ← **Head:** `fix/postgres-mount` --- ### 📝 Commits (3) - [`05a4dd2`](https://github.com/pelican-dev/panel/commit/05a4dd2a911dd3c5ceea8e04cce53964091470e0) Fix weird postgres behavior when selecting mounts - [`b18499c`](https://github.com/pelican-dev/panel/commit/b18499c5b760adf0abf42e7969ae47fc34cc0dae) I think that was unnecessary - [`3a86713`](https://github.com/pelican-dev/panel/commit/3a867134fe8a190bd9422adc14083eb5386dcd4b) Update app/Filament/Admin/Resources/Mounts/MountResource.php ### 📊 Changes **1 file changed** (+2 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `app/Filament/Admin/Resources/Mounts/MountResource.php` (+2 -1) </details> ### 📄 Description Basically I use Pelican with Postgres (I know it's not recommended, but still) and on New Mount page in admin area I get following error: ``` SQLSTATE[42883]: Undefined function: 7 ERROR: could not identify an equality operator for type json LINE 1: select distinct "eggs".* from "eggs" left join "mountables" ... ^ (Connection: pgsql, SQL: select distinct "eggs".* from "eggs" left join "mountables" on "eggs"."id" = "mountables"."mountable_id" order by "eggs"."name" asc limit 50) (View: /var/www/html/vendor/filament/forms/resources/views/components/select.blade.php) (View: /var/www/html/vendor/filament/forms/resources/views/components/select.blade.php) (View: /var/www/html/vendor/filament/forms/resources/views/components/select.blade.php) (View: /var/www/html/vendor/filament/forms/resources/views/components/select.blade.php) (View: /var/www/html/vendor/filament/forms/resources/views/components/select.blade.php) ``` I'm not sure if this the correct solution, but I opted for selecting only distinct id and name to prevent Postgres from comparing JSON columns --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-04 20:00:41 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel#1601
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?