Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

Weird issue with db schema generation when connected to a DO MySQL database

Posted on November 13, 2019

Hi, I’ve opened a ticket but I thought I’d ask here as well in case someone can help. I havre a Rails app that connects to a database in my MySQL cluster managed by DO. If I run migrations on that database, the schema.rb file generated isn’t valid and cannot be used for example for loading into an empty db. If, however, I do exactly the same thing but with a local (Docker) instance of MySQL 8.0.17 - exactly the same version as DO - then all is good. Is there any Rails developer here who could try dumping the schema while connected to DO MySQL?

Thanks!

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

alexdo

June 15, 2023

Hello,

Just came across this answer and decided to write some general guidelines for anyone who comes across this in the future despite the old question.

First, make sure your database.yml file is configured correctly to connect to the DigitalOcean managed MySQL cluster. You should have something like this in your config/database.yml file:

production:
  adapter: mysql2
  encoding: utf8
  url: <%= ENV['DB_URL'] %>
  username: <%= ENV['DB_USERNAME'] %>
  password: <%= ENV['DB_PASSWORD'] %>
  database: <%= ENV['DB_NAME'] %>
  pool: <%= ENV['DB_POOL'] %>

Ensure your environment variables are set correctly in the environment or in your app’s configuration (e.g., using a .env file with the dotenv gem).

After verifying your configuration, run the migrations using:

RAILS_ENV=production bundle exec rake db:migrate

Ensure your local version of MySQL is the same as the one you’re using on DigitalOcean. If the problem persists, please provide more information about the error message you’re receiving, and I’ll do my best to help you further.

For more information on connecting Ruby on Rails with DigitalOcean managed databases, refer to the official documentation.

Hope that this helps!

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.