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

Allow updating conflict table even if the underlying table schema changed. #7775

Merged
merged 3 commits into from
Apr 24, 2024
Merged

Allow updating conflict table even if the underlying table schema changed. #7775

merged 3 commits into from
Apr 24, 2024

Commits on Apr 22, 2024

  1. Re-enable previously skipped tests.

    @nicktobey
    nicktobey committed Apr 22, 2024
    Configuration menu
    Copy the full SHA
    c141c19 View commit details
    Browse the repository at this point in the history

  2. Allow users to update conflict tables if the underlying table had a s… 

    …chema change. This should always be safe, and is necessary in order to manually resolve data conflicts if there was a schema merge.
    @nicktobey
    nicktobey committed Apr 22, 2024
    Configuration menu
    Copy the full SHA
    39275a6 View commit details
    Browse the repository at this point in the history

Commits on Apr 24, 2024

  1. Add clarifying comment on why test is skipped.

    @nicktobey
    nicktobey committed Apr 24, 2024
    Configuration menu
    Copy the full SHA
    a967a85 View commit details
    Browse the repository at this point in the history