Skip to content

Commit 8a9ce17

Browse files
authored
Merge pull request #4337 from ClickHouse/mysql-cascaded-deletes-faq
FAQ for MySQL ON DELETE CASCADE
2 parents ce03fd9 + 3b26afb commit 8a9ce17

File tree

1 file changed

+5
-1
lines changed
  • docs/integrations/data-ingestion/clickpipes/mysql

1 file changed

+5
-1
lines changed

docs/integrations/data-ingestion/clickpipes/mysql/faq.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,4 +37,8 @@ You have several options to resolve these issues:
3737

3838
### Do you support schema changes? {#do-you-support-schema-changes}
3939

40-
Please refer to the [ClickPipes for MySQL: Schema Changes Propagation Support](./schema-changes) page for more information.
40+
Please refer to the [ClickPipes for MySQL: Schema Changes Propagation Support](./schema-changes) page for more information.
41+
42+
### Do you support replicating MySQL foreign key cascading deletes `ON DELETE CASCADE`? {#support-on-delete-cascade}
43+
44+
Due to how MySQL [handles cascading deletes](https://dev.mysql.com/doc/refman/8.0/en/innodb-and-mysql-replication.html), they are not written to the binlog. Therefore it's not possible for ClickPipes (or any CDC tool) to replicate them. This can lead to inconsistent data. It's advised to use triggers instead for supporting cascading deletes.

0 commit comments

Comments
 (0)