Details
Assignee
UnassignedUnassignedReporter
lpjirasynclpjirasync(Deactivated)Priority
LowComponents
Fix versions
Details
Details
Assignee
Unassigned
UnassignedReporter
lpjirasync
lpjirasync(Deactivated)Priority
Components
Fix versions
Smart Checklist
Smart Checklist
Smart Checklist
Created January 24, 2018 at 9:19 PM
Updated January 13, 2024 at 8:54 PM
**Reported in Launchpad by Lars Erler last update 13-12-2016 12:20:03
Please add the following to the documentation of pt-table-sync https://www.percona.com/doc/percona-toolkit/2.1/pt-table-sync.html
pt-table-sync uses "REPLACE INTO", which will fire "insert trigger" in all mysql variants
This can be a huge drawback / data loss (overwrite) risk, if user sets via insert trigger reasonable default values for certain columns / other tables.
Example: "REPLACE INTO products" will fire trigger to set default price in "products_price" and finally overwritten by default value again
What irritates me most is, that there is even a cmd-line option " --[no]check-triggers"
which checks that no triggers are defined on the destination table. Maybe highlight this much more in the doc part.