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

create provenance command #366

Open
agentm opened this issue Feb 27, 2024 · 0 comments
Open

create provenance command #366

agentm opened this issue Feb 27, 2024 · 0 comments
Assignees

Comments

@agentm
Copy link
Owner

agentm commented Feb 27, 2024

One major problem around common SQL database is the issue of "provenance" whereby the who, why, when, what of the table changes is rarely clear or is stored out-of-band. Project:M36 has this information by design, so it should allow users to query how a specific tuple was added to the relvar or how a relvar was constructed- this could include the entire relvar history but also a summary.

Hypothetical:

:provenance s
<commit hash> | [commit hash | rvexpr | commit hash2 | rvexpr2]

Should we just expand the entire transaction graph relevant to the relvar?

@agentm agentm self-assigned this Feb 27, 2024
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

No branches or pull requests

1 participant