|
1 | 1 | --- |
2 | 2 | title: 'MySQL compatibility' |
3 | 3 | subtitle: 'Learn what MySQL syntax, functions, and more are supported by PlanetScale' |
4 | | -date: '2023-12-05' |
| 4 | +date: '2024-08-12' |
5 | 5 | --- |
6 | 6 |
|
7 | 7 | ## Overview |
@@ -48,14 +48,14 @@ If you're attempting to import a database using our Import tool, there are some |
48 | 48 |
|
49 | 49 | ## Miscellaneous |
50 | 50 |
|
51 | | -| Action | Support | Description | |
52 | | -| ----------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
53 | | -| **Empty schemas** | ❌ | Databases with empty schemas are invalid. You cannot deploy a schema change to production if no tables exist. | |
54 | | -| **Non-InnoDB Storage engine** | ❌ | We only support [InnoDB](https://dev.mysql.com/doc/refman/8.0/en/innodb-storage-engine.html) storage engine. | |
55 | | -| **No applicable unique key** | ❌ | We require all tables have a [unique, non-null key](/docs/learn/onlineddl-change-unique-keys) and that respective covered columns are shared between old and new schema. | |
56 | | -| **Direct DDL** | ❌ | We do [not allow Direct DDL](/docs/learn/how-online-schema-change-tools-work) on production branches when [safe migrations](/docs/concepts/safe-migrations) is enabled. This includes `TRUNCATE` statements. | |
57 | | -| **Disabled binary logs** | ❗ | You must have binary logs enabled if importing a database using our [database importer tool](/docs/imports/database-imports). See our [Import doc](/docs/imports/database-imports#server-configuration-issues) for more required configuration. | |
58 | | -| **Large JSON documents** | ❗ | MySQL supports JSON documents up to 1 GB in size. However, we do not recommend to store more than a few MB in a JSON document for performance reasons. | |
| 51 | +| Action | Support | Description | |
| 52 | +| ----------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | |
| 53 | +| **Empty schemas** | ❌ | Databases with empty schemas are invalid. You cannot deploy a schema change to production if no tables exist. | |
| 54 | +| **Non-InnoDB Storage engine** | ❌ | We only support [InnoDB](https://dev.mysql.com/doc/refman/8.0/en/innodb-storage-engine.html) storage engine. | |
| 55 | +| **No applicable unique key** | ❌ | We require all tables have a [unique, non-null key](/docs/learn/onlineddl-change-unique-keys) and that respective covered columns are shared between old and new schema. | |
| 56 | +| **Direct DDL** | ❌ | We do [not allow Direct DDL](/docs/learn/how-online-schema-change-tools-work) on production branches when [safe migrations](/docs/concepts/safe-migrations) is enabled. This includes `TRUNCATE` statements. | |
| 57 | +| **Binary log access** | ❌ | PlanetScale does not currently support binlog replication to external databases. | |
| 58 | +| **Large JSON documents** | ❗ | MySQL supports JSON documents up to 1 GB in size. However, we do not recommend to store more than a few MB in a JSON document for performance reasons. | |
59 | 59 |
|
60 | 60 | ## FAQ |
61 | 61 |
|
|
0 commit comments