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.

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

fix: successive exec of flushdb may cause delete old db fail #2790

Merged

Commits on Jul 9, 2024

  1. 1 add return flag for flushdb

    2 add an atomic flag for flushdb
    3 add callback function when deleted old path
    4 revised some ugly code
    cheniujh committed Jul 9, 2024
    Configuration menu
    Copy the full SHA
    7b125d8 View commit details
    Browse the repository at this point in the history

Commits on Jul 10, 2024

  1. Configuration menu
    Copy the full SHA
    86578e2 View commit details
    Browse the repository at this point in the history
  2. remove debug

    remove debug log
    cheniujh committed Jul 10, 2024
    Configuration menu
    Copy the full SHA
    9a747d2 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    41d82f4 View commit details
    Browse the repository at this point in the history

Commits on Jul 15, 2024

  1. Configuration menu
    Copy the full SHA
    7cd4d95 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    52e14ee View commit details
    Browse the repository at this point in the history

Commits on Jul 16, 2024

  1. removed duplicated logic

    cheniujh committed Jul 16, 2024
    Configuration menu
    Copy the full SHA
    66daa77 View commit details
    Browse the repository at this point in the history