starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-26 09:15:59 +03:00

[GH-ISSUE #1907] [Bug]: Commit `e85c42e` broke the ability to use Koel with Postgres #1032

New issue

Closed

opened 2026-02-26 02:35:00 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 02:35:00 +03:00

Owner

Originally created by @Mar0xy on GitHub (Mar 17, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/1907

Originally assigned to: @phanan on GitHub.

Read the Troubleshooting guide.

I have read and followed the Troubleshooting guide

Reproduction steps

Get latest version
Try to login
Get a SQL error caused by the leftJoin change due to how Postgres works and the server returning an Error.

Expected behavior

No SQL error upon login and being able to actually login

Actual behavior

Postgres erroring out and the website not letting you login due to this issue.

Logs

Noted at the bottom of this issue on the docker repo https://github.com/koel/docker/issues/198

Koel version

7.2.1

How did you install Koel?

Official Docker image

Additional information

Originally created by @Mar0xy on GitHub (Mar 17, 2025). Original GitHub issue: https://github.com/koel/koel/issues/1907 Originally assigned to: @phanan on GitHub. ### Read the Troubleshooting guide. - [x] I have read and followed the Troubleshooting guide ### Reproduction steps 1. Get latest version 2. Try to login 3. Get a SQL error caused by the leftJoin change due to how Postgres works and the server returning an Error. ### Expected behavior No SQL error upon login and being able to actually login ### Actual behavior Postgres erroring out and the website not letting you login due to this issue. ### Logs Noted at the bottom of this issue on the docker repo https://github.com/koel/docker/issues/198 ### Koel version 7.2.1 ### How did you install Koel? Official Docker image ### Additional information

kerem closed this issue

2026-02-26 02:35:00 +03:00

kerem commented

2026-02-26 02:35:00 +03:00

Author

Owner

@Mar0xy commented on GitHub (Mar 17, 2025):

To avoid having to navigate to the other issue here is their output:

database-1  | 2025-03-14 15:20:49.892 UTC [103] ERROR:  column "playlist_playlist_folder.folder_id" must appear in the GROUP BY clause or be used in an aggregate function at character 23
database-1  | 2025-03-14 15:20:49.892 UTC [103] STATEMENT:  select "playlists".*, "playlist_playlist_folder"."folder_id" from "playlists" left join "playlist_playlist_folder" on "playlists"."id" = "playlist_playlist_folder"."playlist_id" where "playlists"."user_id" = $1 group by "playlists"."id"

I have also ran into this exact issue like someone else in the issue and reverting back to 7.2.0 did indeed make it work again in the end but obviously this is just a temp solution.

@Mar0xy commented on GitHub (Mar 17, 2025): To avoid having to navigate to the other issue here is their output: ```txt database-1 | 2025-03-14 15:20:49.892 UTC [103] ERROR: column "playlist_playlist_folder.folder_id" must appear in the GROUP BY clause or be used in an aggregate function at character 23 database-1 | 2025-03-14 15:20:49.892 UTC [103] STATEMENT: select "playlists".*, "playlist_playlist_folder"."folder_id" from "playlists" left join "playlist_playlist_folder" on "playlists"."id" = "playlist_playlist_folder"."playlist_id" where "playlists"."user_id" = $1 group by "playlists"."id" ``` I have also ran into this exact issue like someone else in the issue and reverting back to 7.2.0 did indeed make it work again in the end but obviously this is just a temp solution.

kerem commented

2026-02-26 02:35:00 +03:00

Author

Owner

@phanan commented on GitHub (Mar 17, 2025):

@Mar0xy Thanks for reporting. Interestingly the test didn't catch this bug. I'll take a look.

@phanan commented on GitHub (Mar 17, 2025): @Mar0xy Thanks for reporting. Interestingly the test didn't catch this bug. I'll take a look.

kerem referenced this issue

2026-02-26 03:31:23 +03:00

[PR #1032] [MERGED] Bump fideloper/proxy from 4.1.0 to 4.2.0 #1536

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/koel-koel#1032

No description provided.

Rows
Columns

[GH-ISSUE #1907] [Bug]: Commit e85c42e broke the ability to use Koel with Postgres #1032

Read the Troubleshooting guide.

Reproduction steps

Expected behavior

Actual behavior

Logs

Koel version

How did you install Koel?

Additional information

[GH-ISSUE #1907] [Bug]: Commit `e85c42e` broke the ability to use Koel with Postgres #1032