mirror of
https://github.com/koel/koel.git
synced 2026-04-25 16:56:02 +03:00
[GH-ISSUE #1611] DB errors #886
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#886
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @henrym94 on GitHub (Dec 2, 2022).
Original GitHub issue: https://github.com/koel/koel/issues/1611
When i run "php artisan koel:init"
Next Illuminate\Database\QueryException: SQLSTATE[42000]: Syntax error or access violation: 1074 Column length too big for column 'name' (max = 16383);
how can i fix this? thanks
@nebulade commented on GitHub (Dec 3, 2022):
Was just about to report this as well. In our case this is on mysql v8.
It seems to be hitting https://github.com/koel/koel/blob/master/database/migrations/2021_12_06_164648_increase_string_columns_length.php#L16 although this has not changed since a long time, so maybe some dependency update causes this?
@jSML4ThWwBID69YC commented on GitHub (Dec 4, 2022):
Here too.
Running php artisan koel:init --no-assets
I'm using Galera on MariaDB 10.6.
The issue started with v6.8.2 and exists in v6.8.3. Version 6.8.1 works fine.
@henrym94 commented on GitHub (Dec 4, 2022):
@phanan
@phanan commented on GitHub (Dec 4, 2022):
Looking into it.
@phanan commented on GitHub (Dec 4, 2022):
Fixed (I think) and released in v6.8.4. Thanks everyone for reporting the issue :)
@nebulade commented on GitHub (Dec 5, 2022):
Thanks for the quick fix, I can confirm it is resolved for us.