You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
Should we just expand the entire transaction graph relevant to the relvar?
The text was updated successfully, but these errors were encountered: