Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automatically determine when a table should not use --innodb-optimize-keys #734

Merged
merged 3 commits into from
Jun 19, 2022
Merged

Automatically determine when a table should not use --innodb-optimize-keys #734

merged 3 commits into from
Jun 19, 2022

Commits on Jun 16, 2022

  1. Merge remote-tracking branch 'origin/master' into enh_389

    @davidducos
    davidducos committed Jun 16, 2022
    Configuration menu
    Copy the full SHA
    24b56d7 View commit details
    Browse the repository at this point in the history

Commits on Jun 19, 2022

  1. Automatically determine when a table should not use --innodb-optimize… 

    …-keys
    @davidducos
    davidducos committed Jun 19, 2022
    Configuration menu
    Copy the full SHA
    4442431 View commit details
    Browse the repository at this point in the history

  2. Merge branch 'enh_389' of https://github.com/mydumper/mydumper into e… 

    …nh_389
    @davidducos
    davidducos committed Jun 19, 2022
    Configuration menu
    Copy the full SHA
    a4318f3 View commit details
    Browse the repository at this point in the history