19 points adityamukho 5 hours ago 3 comments
A successor project to my previous attempt at building a temporal graph database (https://news.ycombinator.com/item?id=23455516). This one builds on its predecessor's concept, but drops the dependency on another database to provide the storage, transaction and query engines. Minigraf is self-contained, packaged as a library crate, embeds into your application, and supports full bi-temporality.
adsharma 1 hour ago | parent
Why do you need another database and another query language for this?
Existing cypher based databases which support typed properties (including timestamps) on relationship tables can handle this use case just fine.
ex1fm3ta 31 minutes ago | parent
I feel you, I am completely lost with all new ''graph flavoured DB". I keep challenging those (with the help of Opus model ) and the answer is always the same "use progresql".
Tanjreeve 19 minutes ago | parent
Most graph databases I'm aware of require a server and aren't embedded into applications. Using datalog and applying it to graphs also more general and thus preferable than cypher which is still a niche specifically for graph databases.
Also "because they can" seems obligatory.