~euandreh/public-inbox

1

Progress on 'The database I wish I had'

Details
Message ID
<000001d6d87f$90db0f90$b2912eb0$@kluv.in>
DKIM signature
missing
Download raw message
Hi EuAndreh.

I am curious if you found any existing solution for the proposed database? I
have been looking at irmin (which was mentioned in all forums) a lot lately,
largely as substitute to libgit2, but recently also as a database.

It looks like the conversation have tapered off, or moved elsewhere? In any
case it was interesting stumbling across your post, seeing as I have been
having very similar ideas.

Regards,
Martin
Details
Message ID
<87h7oda5fr.fsf@euandre.org>
In-Reply-To
<000001d6d87f$90db0f90$b2912eb0$@kluv.in> (view parent)
DKIM signature
fail
Download raw message
DKIM signature: fail
<m@kluv.in> writes:

> Hi EuAndreh.

Hi there!

> I am curious if you found any existing solution for the proposed database? I
> have been looking at irmin (which was mentioned in all forums) a lot lately,
> largely as substitute to libgit2, but recently also as a database.

I have written it down as a place to steal ideas from, which I plan to
do in the future as I mature more on the field, but irmin isn't a
solution, being written in OCaml.

> It looks like the conversation have tapered off, or moved elsewhere? In any
> case it was interesting stumbling across your post, seeing as I have been
> having very similar ideas.

I'm working on it, slowly but surely.

The previous "comment" link used to point to my email address first, and
the this public-inbox second. Because of that I had many conversations
done in private messages, where I imagine that people just got the first
link. I responded those in private, but many had similar enough
comments, and I wrote an article on that [0]. FYI: I recently added a
"articles by category" Atom feed, if you prefer a filtered list [1] of
articles.

On the ParsecC project mentioned on the article:
I'm already much more comfortable with creating a C API, but I got to a
point that I needed a proper error handling solution. I stumbled upon an
existing implementation of a parser combinator in C [2].

The point I'm at right now is to read and understand that source code.
In fact, it is 1 of 4 open tabs on my browser right now, before writing
this message.

If I find its error handling good enough, I'll replicate it in ParsecC,
and then in libedn.

I've also started reading a good book on the subject [3]. I can't speak
yet to all of it, but I like what I've seen so far.

I happy to discuss more about it, or answer questions you may have. And
also, I'm happy to accept contributions!

[0]: https://euandre.org/2020/11/12/durable-persistent-trees-and-parser-combinators-building-a-database.html
[1]: https://euandre.org/articles-by-category.html#mediator
[2]: https://github.com/wbhart/Cesium3/tree/combinators
[3]: https://www.immutablearchitecture.com/
Reply to thread Export thread (mbox)