You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I originally reported this in gdpr-dump repo Smile-SA/gdpr-dump#86 but I traced the bug mysqldump-php, I opened a bug at the old repo, as well as this seems more active fork.
When working with large databases, we noticed that generated dump is inconsistent. Some tables will include rows inserted after the dump was initiated. This problem became a dealbreaker with bigger databases.
Tracing this further, it turns out that mysqldump-phpstarts a transaction per table and not for the entire dump process. This is unlike the behavior of the mysqldump command.
The text was updated successfully, but these errors were encountered:
I originally reported this in
gdpr-dump
repo Smile-SA/gdpr-dump#86 but I traced the bugmysqldump-php
, I opened a bug at the old repo, as well as this seems more active fork.When working with large databases, we noticed that generated dump is inconsistent. Some tables will include rows inserted after the dump was initiated. This problem became a dealbreaker with bigger databases.
Tracing this further, it turns out that
mysqldump-php
starts a transaction per table and not for the entire dump process. This is unlike the behavior of themysqldump
command.The text was updated successfully, but these errors were encountered: