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

Overwriting under special circumstances #126

Open
JoanneBogart opened this issue May 23, 2024 · 0 comments
Open

Overwriting under special circumstances #126

JoanneBogart opened this issue May 23, 2024 · 0 comments

Comments

@JoanneBogart
Copy link
Collaborator

Production datasets are never overwritable. But this means if there was any error in the code or other circumstance which interrupted registration of a production dataset, the next attempt must use a different name or version, which can be awkward for legacy datasets. Is this a rare enough occurrence (once we have stable, debugged code) that we just clean up by hand, deleting the unfinished entry?
Or do we allow, not only the data but also the entry to be overwritten if status=0? If the latter, do we need to add yet another argument to DatasetTable.register to request this behavior (but leave the default to not overwrite)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant