AgentM

Just for the record, I think that the original bug opened here is resolved by f1fe611e1bc5d08f2e2b32695169f6aa826cc9f3 which fixes an issue whereby the disconnected transaction used to take a long tuple...

Currently, Project:M36 clients validate the transaction graph via the merkle hashes at connection time. How would you feel about offering the option for clients to skip the validation for trusted...

> That would be nice, but doesn't the server calculate the hashes on every transaction or is it not the case? Also what would be the risk of skipping it,...

I think that this is an interesting debate. In "Out of the Tarpit", the authors make the strong case that the database and application server should be one entity. This...

In 54c822152c71efe71e9e9834a90129cf6ee46798, I fixed an unnecessary bytestring strictness when writing the database to disk. In 0b008bab8ac13f000b41e4ad336a55228787535f, I add BangPatterns to the most common Atoms which reduces data structure indirection and...

> Given your additional notes, to implement something like git I think these are required: > > * Branches should support public/private access levels, possibly with a set of authorized...

> I import a 17 attributes / ~200000 tuples relation. The memory usage jumps from ~2G to ~4G after committing, quitting, and re-entering. And typing in TutorialD becomes slow, which...

It looks like you've identified the cause, but the error could definitely be improved. In this case, the constraint-checking mechanism is complaining that it can't find the required "x" relvar...

I think you are right that, at the very least, the error message when a relvar referenced by a constraint is deleted should be improved.

This is fixed on `346_incdep_errors`. It now looks like: ``` TutorialD (master/main): x:=relation{tuple{name "wow"}} TutorialD (master/main): key unique_name_x {name} x TutorialD (master/main): undefine x ERR: InclusionDependencyCheckError "unique_name_x" (Just (RelVarNotDefinedError "x"))...