# Ghost Database issue with DigitalOcean Database

**URL:** https://forum.ghost.org/t/ghost-database-issue-with-digitalocean-database/19753
**Category:** Installation
**Created:** [January 26, 2021, 3:54pm UTC](https://forum.ghost.org/t/ghost-database-issue-with-digitalocean-database/19753 "2021-01-26T15:54:46Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Andrew\_Belyi](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/andrew_belyi/32/11375_2.png) [@Andrew\_Belyi](https://forum.ghost.org/u/Andrew_Belyi)
#### Post date: [January 26, 2021, 3:54pm UTC](https://forum.ghost.org/t/ghost-database-issue-with-digitalocean-database/19753/1 "2021-01-26T15:54:46Z")

</div>

Hello Ghost team!  
This issue is pretty similar to: [Unable to start ghost in docker with mysql on digitalocean](https://forum.ghost.org/t/unable-to-start-ghost-in-docker-with-mysql-on-digitalocean/17752)

We’re using Digital Ocean’s managed DB MySQL8 for Ghost.  
They require all tables having PKs. Two tables (brute, migrations\_lock) don’t have the keys.I added a column as Primary Key, Auto Inc, Not Null as a workaround to each table.  
**What issues I potentially might face in the future with this workaround when new releases come out?**  
I’m also wondering if there are any plans to add Primary Key to all tables in nearest future?

OS: Ubuntu, v20.04.1 LTS  
Node Version: v12.18.0  
Ghost-CLI Version: v1.15.3  
Ghost Version: v3.40.5  
MySQL Version: v8.0