Upgrade from 0.27.5 to 0.30.2 causes error with php artisan migrate #1894

New Issue

Closed

opened 2026-02-05 02:08:45 +03:00 by OVERLORD · 13 comments

OVERLORD commented 2026-02-05 02:08:45 +03:00

Owner

Copy Link

Originally created by @thelastpsion on GitHub (Oct 10, 2020).

Describe the bug
When upgrading from 0.27.5 to 0.30.2, I get the following error when running php artisan migrate:
Illuminate\Database\QueryException : SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'id'; check that column/key exists (SQL: alter table `joint_permissions` drop `id`)

Steps To Reproduce
Steps to reproduce the behavior:

1. Have installation of 0.27.5
2. Attempt upgrade using git pull origin release && composer install --no-dev && php artisan migrate

Expected behavior
Completion of migration to 0.30.2

Screenshots

Your Configuration (please complete the following information):

• Exact BookStack Version (Found in settings): 0.30.2 (from 0.27.5)
• PHP Version: 7.2.33
• Hosting Method (Nginx/Apache/Docker): Apache

Additional context
Add any other context about the problem here.

Originally created by @thelastpsion on GitHub (Oct 10, 2020). **Describe the bug** When upgrading from 0.27.5 to 0.30.2, I get the following error when running ```php artisan migrate```: ```Illuminate\Database\QueryException : SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'id'; check that column/key exists (SQL: alter table `joint_permissions` drop `id`)``` **Steps To Reproduce** Steps to reproduce the behavior: 1. Have installation of 0.27.5 2. Attempt upgrade using ```git pull origin release && composer install --no-dev && php artisan migrate``` **Expected behavior** Completion of migration to 0.30.2 **Screenshots**  **Your Configuration (please complete the following information):** - Exact BookStack Version (Found in settings): 0.30.2 (from 0.27.5) - PHP Version: 7.2.33 - Hosting Method (Nginx/Apache/Docker): Apache **Additional context** Add any other context about the problem here.

OVERLORD closed this issue 2026-02-05 02:08:48 +03:00

OVERLORD commented 2026-02-05 02:08:50 +03:00

Author

Owner

Copy Link

@ssddanbrown commented on GitHub (Oct 13, 2020):

Hi @PocketNerdIO,
Sorry to hear you're running into issues.

I suspect this is actually due to a different error thrown on original upgrade which has left the database in an awkward state.
I'd suspect this table may be using an old data format.

Before proceeding, Ensure you have a backup of the database.

Coudl you try running the below commands on your database to see if they'd then enable you to migrate as intended?

use bookstack; # Rename to your own database. 
alter table joint_permissions add column id int;
alter table joint_permissions ENGINE=InnoDB;

@ssddanbrown commented on GitHub (Oct 13, 2020): Hi @PocketNerdIO, Sorry to hear you're running into issues. I suspect this is actually due to a different error thrown on original upgrade which has left the database in an awkward state. I'd suspect this table may be using an old data format. **_Before proceeding, Ensure you have a backup of the database._** Coudl you try running the below commands on your database to see if they'd then enable you to migrate as intended? ```sql use bookstack; # Rename to your own database. alter table joint_permissions add column id int; alter table joint_permissions ENGINE=InnoDB; ```

OVERLORD commented 2026-02-05 02:08:53 +03:00

Author

Owner

Copy Link

@gramakri commented on GitHub (Oct 17, 2020):

We hit this in the old Cloudron packages as well. I had to first run "alter table joint_permissions add column id int;". Even after that, we got several duplicate constraint errors. I had to manually remove several rows from the joint_permissions table by hand since there were duplicates of the primary key (which was a 4-tuple). So, I had

a) run alter table joint_permissions add column id int;
b) run migration . it will fail with a constraint violation
c) remove the duplicate row mentioned in step b). now go back to step a)

Unfortunately, I forgot to keep a history of the terminal session, sorry about that. Leaving a note here, in case someone else find it's useful.

@gramakri commented on GitHub (Oct 17, 2020): We hit this in the old Cloudron packages as well. I had to first run "alter table joint_permissions add column id int;". Even after that, we got several duplicate constraint errors. I had to manually remove several rows from the joint_permissions table by hand since there were duplicates of the primary key (which was a 4-tuple). So, I had a) run alter table joint_permissions add column id int; b) run migration . it will fail with a constraint violation c) remove the duplicate row mentioned in step b). now go back to step a) Unfortunately, I forgot to keep a history of the terminal session, sorry about that. Leaving a note here, in case someone else find it's useful.

OVERLORD commented 2026-02-05 02:08:55 +03:00

Author

Owner

Copy Link

@QuaverSager commented on GitHub (Oct 30, 2020):

Hello!
I'm completely new to doing a project like this. With no experience with programming.
@ssddanbrown how would one write out those commands for Windows Command Line?

@QuaverSager commented on GitHub (Oct 30, 2020): Hello! I'm completely new to doing a project like this. With no experience with programming. @ssddanbrown how would one write out those commands for Windows Command Line?

OVERLORD commented 2026-02-05 02:09:00 +03:00

Author

Owner

Copy Link

@ssddanbrown commented on GitHub (Nov 2, 2020):

Hi @QuaverSager,
Those commands are intended to be ran against the database (MySQL or MariaDB).
How you access that will really depend on how you've installed BookStack and the database. I can try to help further if you can explain your setup/install process.

@ssddanbrown commented on GitHub (Nov 2, 2020): Hi @QuaverSager, Those commands are intended to be ran against the database (MySQL or MariaDB). How you access that will really depend on how you've installed BookStack and the database. I can try to help further if you can explain your setup/install process.

OVERLORD commented 2026-02-05 02:09:02 +03:00

Author

Owner

Copy Link

@QuaverSager commented on GitHub (Nov 3, 2020):

@ssddanbrown Thank you!
I've been using this video as a guide: https://youtu.be/lSaY4lK_RjM
Naming and putting files in nearly the exact setup since I'm unfamiliar with this.
And I've been running all the commands via the windows command-line interface, same as in the video.

@QuaverSager commented on GitHub (Nov 3, 2020): @ssddanbrown Thank you! I've been using this video as a guide: https://youtu.be/lSaY4lK_RjM Naming and putting files in nearly the exact setup since I'm unfamiliar with this. And I've been running all the commands via the windows command-line interface, same as in the video.

OVERLORD commented 2026-02-05 02:09:08 +03:00

Author

Owner

Copy Link

@ssddanbrown commented on GitHub (Nov 3, 2020):

@QuaverSager Okay, Following the guide at timestamp 10:44 it looks like you would have used PHPmyAdmin to set up the database for BookStack?

If so, Login as you would have in that guide at 10:44.

---

Before you go any further, Backup your database. Click the "Home" icon under the phpMyAdmin logo in the top left, Click on the "Export" tab at the top. On that page, The "Export Method" should be "quick" and "Format" should be "SQL". Click "Go" in the bottom right then store that sql file somewhere safely. If this process fails do not continue.

---

Now, to run the commands, Click your bookstack table in the left column to select it. At the top click on the "SQL" tab. This should show a big text box with "Run SQL query/queries on database bookstack" above it.
You can paste the commands in there then press the "Go" button in the bottom right corner.

That should be it, now you can re-attempt the upgrade.

@ssddanbrown commented on GitHub (Nov 3, 2020): @QuaverSager Okay, Following the guide at timestamp 10:44 it looks like you would have used PHPmyAdmin to set up the database for BookStack? If so, Login as you would have in that guide at 10:44. --- **Before you go any further, Backup your database**. Click the "Home" icon under the phpMyAdmin logo in the top left, Click on the "Export" tab at the top. On that page, The "Export Method" should be "quick" and "Format" should be "SQL". Click "Go" in the bottom right then store that sql file somewhere safely. If this process fails do not continue. --- Now, to run the commands, Click your `bookstack` table in the left column to select it. At the top click on the "SQL" tab. This should show a big text box with "Run SQL query/queries on database bookstack" above it. You can paste the commands in there then press the "Go" button in the bottom right corner. That should be it, now you can re-attempt the upgrade.

OVERLORD commented 2026-02-05 02:09:11 +03:00

Author

Owner

Copy Link

@ruben-rodriguez commented on GitHub (Nov 9, 2020):

I was also getting this issue, after running

use bookstack; # Rename to your own database. 
alter table joint_permissions add column id int;
alter table joint_permissions ENGINE=InnoDB;

I was getting:

Starting Migration...
Migrating: 2020_08_04_111754_drop_joint_permissions_id
Illuminate\Database\QueryException  : SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '4-BookStack\Chapter-4-page-create' for key 'PRIMARY' (SQL: alter table `joint_permissions` add primary key `joint_primary`(`role_id`, `entity_type`, `entity_id`, `action`))

at /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Connection.php:669
     665|         // If an exception occurs when attempting to run a query, we'll format the error
     666|         // message to include the bindings with SQL, which will make this exception a
     667|         // lot more helpful to the developer instead of just the database's errors.
     668|         catch (Exception $e) {
   > 669|             throw new QueryException(
     670|                 $query, $this->prepareBindings($bindings), $e
     671|             );
     672|         }
     673|

  Exception trace:

   1   Doctrine\DBAL\Driver\PDOException::("SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '4-BookStack\Chapter-4-page-create' for key 'PRIMARY'")
       /var/www/bookstack/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:131

  2   PDOException::("SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '4-BookStack\Chapter-4-page-create' for key 'PRIMARY'")
      /var/www/bookstack/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:129

Effectively, when trying to run such alter table to add that primary key it failed:

alter table `joint_permissions` add primary key `joint_primary`(`role_id`, `entity_type`, `entity_id`, `action`);
ERROR 1062 (23000): Duplicate entry '1-BookStack\Book-4-chapter-create' for key 'PRIMARY'

Finally made it work by:
1 - Adding ID column.
2 - Removing duplicates by running the primary key alter with IGNORE
3 - Dropping the primary key so Syntax error or access violation: 1068 Multiple primary key defined is not triggered.
4 - Trying again migration process.

use bookstack; # Rename to your own database. 
alter table joint_permissions add column id int;
alter table joint_permissions ENGINE=InnoDB;
alter ignore table `joint_permissions` add primary key `joint_primary`(`role_id`, `entity_type`, `entity_id`, `action`);
alter table `joint_permissions` drop primary key;

It is now working fine 😎

@ruben-rodriguez commented on GitHub (Nov 9, 2020): I was also getting this issue, after running ``` use bookstack; # Rename to your own database. alter table joint_permissions add column id int; alter table joint_permissions ENGINE=InnoDB; ``` I was getting: ``` Starting Migration... Migrating: 2020_08_04_111754_drop_joint_permissions_id Illuminate\Database\QueryException : SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '4-BookStack\Chapter-4-page-create' for key 'PRIMARY' (SQL: alter table `joint_permissions` add primary key `joint_primary`(`role_id`, `entity_type`, `entity_id`, `action`)) at /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Connection.php:669 665| // If an exception occurs when attempting to run a query, we'll format the error 666| // message to include the bindings with SQL, which will make this exception a 667| // lot more helpful to the developer instead of just the database's errors. 668| catch (Exception $e) { > 669| throw new QueryException( 670| $query, $this->prepareBindings($bindings), $e 671| ); 672| } 673| Exception trace: 1 Doctrine\DBAL\Driver\PDOException::("SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '4-BookStack\Chapter-4-page-create' for key 'PRIMARY'") /var/www/bookstack/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:131 2 PDOException::("SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '4-BookStack\Chapter-4-page-create' for key 'PRIMARY'") /var/www/bookstack/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:129 ``` Effectively, when trying to run such alter table to add that primary key it failed: ``` alter table `joint_permissions` add primary key `joint_primary`(`role_id`, `entity_type`, `entity_id`, `action`); ERROR 1062 (23000): Duplicate entry '1-BookStack\Book-4-chapter-create' for key 'PRIMARY' ``` Finally made it work by: 1 - Adding ID column. 2 - Removing duplicates by running the primary key alter with IGNORE 3 - Dropping the primary key so ```Syntax error or access violation: 1068 Multiple primary key defined``` is not triggered. 4 - Trying again migration process. ``` use bookstack; # Rename to your own database. alter table joint_permissions add column id int; alter table joint_permissions ENGINE=InnoDB; alter ignore table `joint_permissions` add primary key `joint_primary`(`role_id`, `entity_type`, `entity_id`, `action`); alter table `joint_permissions` drop primary key; ``` It is now working fine 😎

OVERLORD commented 2026-02-05 02:09:15 +03:00

Author

Owner

Copy Link

@QuaverSager commented on GitHub (Dec 18, 2020):

@ssddanbrown Thank you so much! That helped me get past where I was stuck.

@QuaverSager commented on GitHub (Dec 18, 2020): @ssddanbrown Thank you so much! That helped me get past where I was stuck.

OVERLORD commented 2026-02-05 02:09:19 +03:00

Author

Owner

Copy Link

@ssddanbrown commented on GitHub (Jan 2, 2021):

Due to the lack of response from the original issue author I will close this. Thanks to everyone above that's provided support or advice.

@ssddanbrown commented on GitHub (Jan 2, 2021): Due to the lack of response from the original issue author I will close this. Thanks to everyone above that's provided support or advice.

OVERLORD commented 2026-02-05 02:09:22 +03:00

Author

Owner

Copy Link

@samang-dauth commented on GitHub (Jan 5, 2021):

Migrating: 2020_08_04_111754_drop_joint_permissions_id

Illuminate\Database\QueryException : SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'id'; check that column/key exists (SQL: alter table joint_permissions drop id)

at */vendor/laravel/framework/src/Illuminate/Database/Connection.php:669
665| // If an exception occurs when attempting to run a query, we'll format the error
666| // message to include the bindings with SQL, which will make this exception a
667| // lot more helpful to the developer instead of just the database's errors.
668| catch (Exception $e) {

669| throw new QueryException(
670| $query, $this->prepareBindings($bindings), $e
671| );
672| }
673|

Exception trace:

1 Doctrine\DBAL\Driver\PDOException::("SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'id'; check that column/key exists")
*/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:131

2 PDOException::("SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'id'; check that column/key exists")
*/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:129

Please use the argument -v to see more details.

@samang-dauth commented on GitHub (Jan 5, 2021): Migrating: 2020_08_04_111754_drop_joint_permissions_id Illuminate\Database\QueryException : SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'id'; check that column/key exists (SQL: alter table `joint_permissions` drop `id`) at */vendor/laravel/framework/src/Illuminate/Database/Connection.php:669 665| // If an exception occurs when attempting to run a query, we'll format the error 666| // message to include the bindings with SQL, which will make this exception a 667| // lot more helpful to the developer instead of just the database's errors. 668| catch (Exception $e) { > 669| throw new QueryException( 670| $query, $this->prepareBindings($bindings), $e 671| ); 672| } 673| Exception trace: 1 Doctrine\DBAL\Driver\PDOException::("SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'id'; check that column/key exists") */vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:131 2 PDOException::("SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'id'; check that column/key exists") */vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:129 Please use the argument -v to see more details.

OVERLORD commented 2026-02-05 02:09:25 +03:00

Author

Owner

Copy Link

@samang-dauth commented on GitHub (Jan 5, 2021):

I have run the command as above following @ssddanbrown but it still not fix and the error still exists.

@samang-dauth commented on GitHub (Jan 5, 2021): I have run the command as above following @ssddanbrown but it still not fix and the error still exists.

OVERLORD commented 2026-02-05 02:09:27 +03:00

Author

Owner

Copy Link

@samang-dauth commented on GitHub (Jan 5, 2021):

The migration is successful, but when I log in with default admin it is shown below. I had tried to install with many times with a fresh server, but still getting this error. Anyone can help me to solve it?

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'owned_by' in 'where clause' (SQL: select * from activities where (exists (select id from joint_permissions where joint_permissions.entity_id=activities.entity_id and joint_permissions.entity_type=activities.entity_type and action = view and role_id in (1) and (has_permission = 1 or (has_permission_own = 1 and owned_by = 1)))) order by created_at desc limit 10 offset 0)

@samang-dauth commented on GitHub (Jan 5, 2021): The migration is successful, but when I log in with default admin it is shown below. I had tried to install with many times with a fresh server, but still getting this error. Anyone can help me to solve it? SQLSTATE[42S22]: Column not found: 1054 Unknown column 'owned_by' in 'where clause' (SQL: select * from `activities` where (exists (select `id` from `joint_permissions` where joint_permissions.entity_id=activities.entity_id and joint_permissions.entity_type=activities.entity_type and `action` = view and `role_id` in (1) and (`has_permission` = 1 or (`has_permission_own` = 1 and `owned_by` = 1)))) order by `created_at` desc limit 10 offset 0)

OVERLORD commented 2026-02-05 02:09:29 +03:00

Author

Owner

Copy Link

@ssddanbrown commented on GitHub (Jan 5, 2021):

Hi @tolaleng,
This issue is closed so it's easy to miss things here.

Can you open a new issue for this? And in that issue please paste the output of running php artisan migrate:status.

@ssddanbrown commented on GitHub (Jan 5, 2021): Hi @tolaleng, This issue is closed so it's easy to miss things here. Can you open a new issue for this? And in that issue please paste the output of running `php artisan migrate:status`.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

development

further_theme_development

l10n_development

release

llm_only

vectors

v25-11

docker_env

drawio_rendering

user_permissions

ldap_host_failover

svg_image

prosemirror

captcha_example

fix/video-export

v25.12.3

v25.12.2

v25.12.1

v25.12

v25.11.6

v25.11.5

v25.11.4

v24.11.4

v25.11.3

v25.11.2

v25.11.1

v25.11

v25.07.3

v25.07.2

v25.07.1

v25.07

v25.05.2

v25.05.1

v25.05

v25.02.5

v25.02.4

v25.02.3

v25.02.2

v25.02.1

v25.02

v24.12.1

v24.12

v24.10.3

v24.10.2

v24.10.1

v24.10

v24.05.4

v24.05.3

v24.05.2

v24.05.1

v24.05

v24.02.3

v24.02.2

v24.02.1

v24.02

v23.12.3

v23.12.2

v23.12.1

v23.12

v23.10.4

v23.10.3

v23.10.2

v23.10.1

v23.10

v23.08.3

v23.08.2

v23.08.1

v23.08

v23.06.2

v23.06.1

v23.06

v23.05.2

v23.05.1

v23.05

v23.02.3

v23.02.2

v23.02.1

v23.02

v23.01.1

v23.01

v22.11.1

v22.11

v22.10.2

v22.10.1

v22.10

v22.09.1

v22.09

v22.07.3

v22.07.2

v22.07.1

v22.07

v22.06.2

v22.06.1

v22.06

v22.04.2

v22.04.1

v22.04

v22.03.1

v22.03

v22.02.3

v22.02.2

v22.02.1

v22.02

v21.12.5

v21.12.4

v21.12.3

v21.12.2

v21.12.1

v21.12

v21.11.3

v21.11.2

v21.11.1

v21.11

v21.10.3

v21.10.2

v21.10.1

v21.10

v21.08.6

v21.08.5

v21.08.4

v21.08.3

v21.08.2

v21.08.1

v21.08

v21.05.4

v21.05.3

v21.05.2

v21.05.1

v21.05

v21.04.6

v21.04.5

v21.04.4

v21.04.3

v21.04.2

v21.04.1

v21.04

v0.31.8

v0.31.7

v0.31.6

v0.31.5

v0.31.4

v0.31.3

v0.31.2

v0.31.1

v0.31.0

v0.30.7

v0.30.6

v0.30.5

v0.30.4

v0.30.3

v0.30.2

v0.30.1

v0.30.0

v0.29.3

v0.29.2

v0.29.1

v0.29.0

v0.28.3

v0.28.2

v0.28.1

v0.28.0

v0.27.5

v0.27.4

v0.27.3

v0.27.2

v0.27.1

v0.27

v0.26.4

v0.26.3

v0.26.2

v0.26.1

v0.26.0

v0.25.5

v0.25.4

v0.25.3

v0.25.2

v0.25.1

v0.25.0

v0.24.3

v0.24.2

v0.24.1

v0.24.0

v0.23.2

v0.23.1

v0.23.0

v0.22.0

v0.21.0

v0.20.3

v0.20.2

v0.20.1

v0.20.0

v0.19.0

v0.18.5

v0.18.4

v0.18.3

v0.18.2

v0.18.1

v0.18.0

v0.17.4

v0.17.3

v0.17.2

v0.17.1

v0.17.0

v0.16.3

v0.16.2

v0.16.1

v0.16.0

v0.15.3

v0.15.2

v0.15.1

v0.15.0

v0.14.3

v0.14.2

v0.14.1

v0.14.0

v0.13.1

v0.13.0

v0.12.2

v0.12.1

v0.12.0

v0.11.2

v0.11.1

v0.11.0

v0.10.0

v0.9.3

v0.9.2

v0.9.1

v0.9.0

v0.8.2

v0.8.1

v0.8.0

v0.7.6

v0.7.5

v0.7.4

v0.7.3

0.7.2

v.0.7.1

v0.7.0

v0.6.3

v0.6.2

v0.6.1

v0.6.0

v0.5.0

Labels

Clear labels

🎨 Design

📖 Docs Update

🐛 Bug

🐛 Bug

:cat2:🐈 Possible duplicate

💿 Database

☕ Open to discussion

💻 Front-End

🐕 Support

🚪 Authentication

🌍 Translations

🔌 API Task

🏭 Back-End

⛲ Upstream

🔨 Feature Request

🛠️ Enhancement

🛠️ Enhancement

🛠️ Enhancement

❤️ Happy feedback

🔒 Security

🔍 Pending Validation

💆 UX

📝 WYSIWYG Editor

🌔 Out of scope

🔩 API Request

:octocat: Admin/Meta

🖌️ View Customization

❓ Question

🚀 Priority

🛡️ Blocked

🚚 Export System

♿ A11y

🔧 Maintenance

> Markdown Editor

pull-request

Mirrored from GitHub Pull Request

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

OVERLORD

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#1894