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

Cloning fixes #172

Merged
merged 5 commits into from
Oct 19, 2023
Merged

Cloning fixes #172

merged 5 commits into from
Oct 19, 2023

Conversation

mikedarcy
Copy link
Collaborator

No description provided.

karlcz and others added 5 commits June 1, 2023 18:27
1. simplify handling of special ermrest tables using onconflict=skip
2. defer acl_bindings until after fkeys are provisioned
3. add ERMrest_RID_Lease handling to skip data cloning
The original cloning logic failed to account for applying configuration
changes to tables that already exist in the destination catalog. This
is usually just the built-in ERMrest tables in the public schema,
but could include others if the caller supplies the destination catalog
as an input argument.

To be safe, apply all configuration again in the final phase. The
normal apply() logic tries to avoid unnecessary requests and so should
be efficient. Also, we do not want to revert the cloning status
state value already written into the destination table annotations
by earlier clone processing stages, so that gets special handling.
@mikedarcy mikedarcy requested a review from karlcz October 13, 2023 19:57
@mikedarcy mikedarcy merged commit b4dc2e7 into master Oct 19, 2023
@mikedarcy mikedarcy deleted the cloning_fixes branch January 12, 2024 21:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants