Page MenuHomePhabricator

[docs] Switch from MySQL to MariaDB
ClosedPublic

Authored by ashoat on Jul 19 2022, 1:04 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Nov 2, 6:21 PM
Unknown Object (File)
Thu, Oct 24, 9:56 AM
Unknown Object (File)
Oct 23 2024, 7:26 AM
Unknown Object (File)
Oct 7 2024, 12:05 PM
Unknown Object (File)
Oct 7 2024, 12:05 PM
Unknown Object (File)
Oct 7 2024, 12:05 PM
Unknown Object (File)
Oct 7 2024, 11:56 AM
Unknown Object (File)
Oct 7 2024, 4:52 AM

Details

Summary

This updates our dev environment instructions to tell the user to install MariaDB instead of MySQL.

Test Plan

I ran these instructions on my own machine and confirmed things work. I also created this Gist with instructions for migrating

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

docs/dev_environment.md
125 ↗(On Diff #14667)

I added a note here to explain why we're still using "mysql" commands

128 ↗(On Diff #14667)

This isn't necessary anywhere since the Brew mariadb keg isn't "keg-only" like the mysql@5.7 (versioned ones are usually keg-only, but unversioned usually aren't)

Was able to switch over from MySQL to MariaDB on my MacBook. I can confirm that TablePlus continues to work with the steps in this doc.

After following the steps, I ran into:

ERROR 1006 (HY000): Can't create database 'comm' (errno: 2 "No such file or directory")

when I tried running:

CREATE DATABASE comm;

After minimal research online, it seemed like it was a permissions-related issue. I decided to restart my computer on a whim (I'd stopped the mysql service and uninstalled and unlinked mysql@5.7, but figured just in case there was something still lingering from the previous mysql installation?), and that seemed to resolve the issue for me.

I realize "restart your computer" isn't a great solution nor does it help determine the root cause... but it got things working for me.

This revision is now accepted and ready to land.Jul 19 2022, 2:44 PM

Realized that something is a bit borked with backup/restore on MariaDB, so holding off on this for now

This revision is now accepted and ready to land.Jul 26 2022, 4:37 AM
This revision was automatically updated to reflect the committed changes.