[GH-ISSUE #138] Installation with PostgreSQL #94

Closed
opened 2026-02-26 02:32:07 +03:00 by kerem · 4 comments
Owner

Originally created by @Roudaille77 on GitHub (Dec 23, 2015).
Original GitHub issue: https://github.com/koel/koel/issues/138

Hi,
I am happy to have discover Koel, thanks you for this great app ! I just want to share my experience of using it with a Postgres database (on my Raspberry Pi 2). I have added this line in my .env file :
DB_CONNECTION=pgsql.
Then to avoid unique constraint violations when adding songs to library, execute those queries before setting your media path :

ALTER SEQUENCE artists_id_seq RESTART WITH 2;
ALTER SEQUENCE albums_id_seq RESTART WITH 2;

It seems that Unknown artist and Unknown album with id 1 aren't correctly seen by Postgres !

Originally created by @Roudaille77 on GitHub (Dec 23, 2015). Original GitHub issue: https://github.com/koel/koel/issues/138 Hi, I am happy to have discover Koel, thanks you for this great app ! I just want to share my experience of using it with a Postgres database (on my Raspberry Pi 2). I have added this line in my `.env` file : `DB_CONNECTION=pgsql`. Then to avoid unique constraint violations when adding songs to library, execute those queries before setting your media path : ``` ALTER SEQUENCE artists_id_seq RESTART WITH 2; ALTER SEQUENCE albums_id_seq RESTART WITH 2; ``` It seems that `Unknown artist` and `Unknown album` with id `1` aren't correctly seen by Postgres !
kerem closed this issue 2026-02-26 02:32:07 +03:00
Author
Owner

@funcoding commented on GitHub (Dec 23, 2015):

I think it's a prob with auto incrementing value in Postgres. This may help. I shall try to send a PR if possible.

<!-- gh-comment-id:166940199 --> @funcoding commented on GitHub (Dec 23, 2015): I think it's a prob with auto incrementing value in Postgres. [This may help](https://laracasts.com/discuss/channels/requests/eloquent-and-postgresql-incrementing). I shall try to send a PR if possible.
Author
Owner

@sammcj commented on GitHub (Dec 23, 2015):

+1 for replacing MySQL with PostgreSQL, it's generally considerably faster, better-designed, more standards-compliant, more consistent and is generally more programmer-friendly.

<!-- gh-comment-id:167000895 --> @sammcj commented on GitHub (Dec 23, 2015): +1 for replacing MySQL with PostgreSQL, it's generally considerably faster, better-designed, more standards-compliant, more consistent and is generally more programmer-friendly.
Author
Owner

@jommgoncalves commented on GitHub (Dec 24, 2015):

+1 for replacing MySQL with PostgreSQL

<!-- gh-comment-id:167013768 --> @jommgoncalves commented on GitHub (Dec 24, 2015): +1 for replacing MySQL with PostgreSQL
Author
Owner

@phanan commented on GitHub (Dec 24, 2015):

We're not here to discuss which technology is better – I'm sick of these "discussions" frankly saying. Come back when you think you have reached the limitation of MySQL, or any RDBMS for that matter, with Koel.

<!-- gh-comment-id:167039965 --> @phanan commented on GitHub (Dec 24, 2015): We're not here to discuss which technology is better – I'm sick of these "discussions" frankly saying. Come back when you think you have reached the limitation of MySQL, or any RDBMS for that matter, with Koel.
Sign in to join this conversation.
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#94
No description provided.