Existing cypher based databases which support typed properties (including timestamps) on relationship tables can handle this use case just fine.

forgive my ignorance on such a basic concept. I read 'Embedded' as in 'for Embedded systems'

Does it mean 'Embedded in your rust application'?

It also used datalog, written in rust

Great to see tho, I'm always eagerly hoping for a successful embedded graph database. Most recently my hope was for kuzudb, but they got acquihired; though it's still open-sourcing' as LadybugDB.

Highly recommend taking inspiration from Kuzudb/Ladybugdb and cozodb.

Godspeed!

LLM memory.. let's say, architecturally, its suitable for storing and processing queries - is questionable, but okay. But what real-world use case would generate such queries? It seems to me that the context for formulating and processing the results would be orders of magnitude greater than simply writing down what's needed in plain text. If my notebook took the form of a temporal multiverse of entities, I'd lose the ability to use it properly.

But maybe I'm just too old to quickly get the hang of every new type of Pokémon.

P.S. I'm using the built-in SQLite to store a graph with up to 10 million edges in an MCP app I'm developing for working with code.