Explore >> Select a destination
|
You are here 
|
planetscale.com | ||
| | | | |
vitess.io
|
|
| | | | | An in-depth technical discussion on the limitations of foreign keys in MySQL and why the can't play nicely with online DDL | |
| | | | |
nick.zoic.org
|
|
| | | | | [AI summary] The post explains the error caused by defining foreign keys between InnoDB and MyISAM tables in MySQL and MariaDB, offering a solution to migrate legacy tables to InnoDB. | |
| | | | |
antzucaro.com
|
|
| | | | | The Scenario Let's suppose you are modeling a database in MySQL 5.5. Based on your knowledge of the requirements for the application behind this database you can guess which of the tables within it are going to be huge. For those huge tables you want to plan ahead to make sure that you can scale out your data such that you have less headaches in the future. Here's the catch: you want to keep it simple until it comes time to scale out. | |
| | | | |
jvns.ca
|
|
| | | SQL queries don't start with SELECT | ||
