The problem with MySQL foreign key constraints in Online Schema Changes (2021)
(openark.org)
This post explains the inherent problem of running online schema changes in MySQL, on tables participating in a foreign key relationship. We’ll lay some ground rules and facts, sketch a simplified schema, and dive into an online schema change operation.
This post explains the inherent problem of running online schema changes in MySQL, on tables participating in a foreign key relationship. We’ll lay some ground rules and facts, sketch a simplified schema, and dive into an online schema change operation.
Meta's MySQL Fork You Never Knew About
(kirshatrov.com)
It's not very well widely known — but in the world of MySQL forks like Percona and MariaDB, Facebook's fork might be the most interesting one!
It's not very well widely known — but in the world of MySQL forks like Percona and MariaDB, Facebook's fork might be the most interesting one!
Show HN: WeSQL – An Innovative MySQL That Stores All Data on S3
(github.com/wesql)
WeSQL is an innovative MySQL distribution that adopts a compute-storage separation architecture, with storage backed by S3 (and S3-compatible systems). It can run on any cloud, ensuring no vendor lock-in.
WeSQL is an innovative MySQL distribution that adopts a compute-storage separation architecture, with storage backed by S3 (and S3-compatible systems). It can run on any cloud, ensuring no vendor lock-in.
Evolving Intercom's Database Infrastructure
(intercom.com)
Intercom is rolling out a major evolution of our database architecture moving to Vitess – a scalable, open-source MySQL clustering system – managed by PlanetScale.
Intercom is rolling out a major evolution of our database architecture moving to Vitess – a scalable, open-source MySQL clustering system – managed by PlanetScale.
In MySQL, never use "UTF8". Use "utf8mb4"
(medium.com)
Today’s bug: I tried to store a UTF-8 string in a MariaDB “utf8”-encoded database, and Rails raised a bizarre error:
Today’s bug: I tried to store a UTF-8 string in a MariaDB “utf8”-encoded database, and Rails raised a bizarre error: