AgentM

Sessions are referenced by a unique identifier so that sessions could conceivably outlive connections. One connection could pass the session id to another connection to share or take over a...

A potential use-case for persistent sessions could be the desire to share uncommitted state between multiple clients. That could be useful for change review before commit.

Interesting, indeed! Thanks for the link. I have contacted the authors of the paper for more details.

The paper can be found [here](https://msfp-workshop.github.io/msfp2020/henglein-mathiesen.pdf). The paper also mentions "[Factorized Databases](https://fdbresearch.github.io)", a tree-based representations of joins which [purports](https://fdbresearch.github.io/principles/second-example.html) to provide an redundancy-free representation.

Project:M36 already has a notion similar to factorized joins in nested relations. It may be interesting to implement a special form of join which generates nested relation results.

After reviewing the paper and the video, it's not immediately clear but strongly implied that this optimization applies only to the "triangle join" query which finds triples that reference each...

Project:M36 supports two methods of implementing extensions: * Haskell pre-compiled into the binaries (ideal for bridges to Haskell data types) * runtime-compiled Haskell via GHC-as-a-service (ideal for third-party modules) Beyond...

Sounds good. If you need live help, join us in our IRC channel at chat.freenode.net #project-m36

I have mulled over this, too, but this could get complicated because we would need to break out a separate remote client library. The current ```ProjectM36.Client``` provides identical interfaces for...

Thanks for the link- I wasn't aware of that project. A good start on this ticket would be a sort of schema diff tool and schema hashing. I think that...