docs: upstream

planetscale/www@18eaa3c

docs/reference/mysql-compatibility.md

@@ -44,6 +44,7 @@ If you're attempting to import a database using our Import tool, there are some
 | `PIPES_AS_CONCAT`             | ❌      | Enabling this SQL mode can interfere with Vitess' evalengine parsing the SQL queries so enabling it may result in incorrect or unexpected results. Please use MySQL's standard dialect instead, e.g. `CONCAT()`.                                           |
 | `ANSI_QUOTES`                 | ❌      | Enabling this SQL mode can interfere with Vitess' evalengine parsing the SQL queries so enabling it may result in incorrect or unexpected results. Please use MySQL's standard quotation instead.                                                          |
 | `INSERT ... AS ...`           | ❌      | In an `INSERT ... AS ...` statement, aliasing the columns or rows is not yet supported.                                                                                                                                                                    |
+| `WITH RECURSIVE`              | ❌      | We do not support recursive common table expressions (CTEs)                                                                                                                                                                                                |
 
 ## Miscellaneous
 
@@ -52,7 +53,7 @@ If you're attempting to import a database using our Import tool, there are some
 | **Empty schemas**             | ❌      | Databases with empty schemas are invalid. You cannot deploy a schema change to production if no tables exist.                                                                                                                                   |
 | **Non-InnoDB Storage engine** | ❌      | We only support [InnoDB](https://dev.mysql.com/doc/refman/8.0/en/innodb-storage-engine.html) storage engine.                                                                                                                                    |
 | **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.                                                                        |
-| **Direct DDL**                | ❌      | We do [not allow Direct DDL](/docs/learn/how-online-schema-change-tools-work) on [production branches](/docs/concepts/branching). This includes `TRUNCATE` statements.                                                                          |
+| **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.                                    |
 | **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. |
 | **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.                                                                                          |