php artisan migrate fails when migrating from V0.23 #1027
Labels
No labels
Focus: A11y
Focus: Admin/Meta
Focus: Authentication
Focus: Back-End
Focus: Database
Focus: Design & UX
Focus: Editor - Markdown
Focus: Editor - WYSIWYG
Focus: Export System
Focus: Front-End
Focus: Translations
Focus: View Customization
Is: Docs Update
Is: Enhancement
Is: Priority
Is: Security
Is: Upstream
Status
Blocked
Status
Open to discussion
Status
Out of scope
Status
Pending Validation
Type
API Request
Type
Bug Report
Type
Feature Request
Type
Happy feedback
Type
Maintenance
Type
Question
Type
Support
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
bookstack/bookstack#1027
Loading…
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?
Describe the bug
php artisan migratefails when migrating from V0.23Steps To Reproduce
Steps to reproduce the behavior:
git pull origin release && composer install && php artisan migrateExpected behavior
Migrate to complete successfully.
Screenshots

Your Configuration (please complete the following information):
Additional context
I have had this happen on 2 different instances.
Same issue here, coming from 0.22.0.
On subsequent attempts:
And here's the copy-able text:
Thanks for reporting @NathanVaughn & @Jekotia.
Can either of you confirm MySQL versions?
And also, At any point, Have either of you been using MySQL 5.5 with BookStack?
Checking the engine used on the
bookstable would be a big help, To see if it's InnoDB or MyISAM.@ssddanbrown
$ mysql --version
mysql Ver 14.14 Distrib 5.7.21, for Linux (x86_64) using EditLine wrapper
According to
SHOW TABLE STATUS\Gall tables are InnoDB except for the following, which are MyISAM:@Jekotia Thanks for confirming, Just creating a patch now.
@ssddanbrown I manually applied the above commit and this is now the result when trying to migrate
@Jekotia Yeah, Came across that also, Just debugging it now.
@Jekotia @NathanVaughn Okay, Just pushed out a new release. Please try again. Hopefully should be covered now. Please confirm here how the upgrade want. Apologies for this issue.
The new release worked perfectly for me. Thanks so much @ssddanbrown.
Awesome, Hopefully that covers everything. Will close this then.
Fixed here as well. Thank you for the prompt resolution!