Skip to content
This repository was archived by the owner on Nov 12, 2024. It is now read-only.

Commit bba313d

Browse files
1 parent dbaeb2c commit bba313d

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docs/reference/mysql-compatibility.md

+9-9
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: 'MySQL compatibility'
33
subtitle: 'Learn what MySQL syntax, functions, and more are supported by PlanetScale'
4-
date: '2023-12-05'
4+
date: '2024-08-12'
55
---
66

77
## Overview
@@ -48,14 +48,14 @@ If you're attempting to import a database using our Import tool, there are some
4848

4949
## Miscellaneous
5050

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. |
5959

6060
## FAQ
6161

0 commit comments

Comments
 (0)