git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git for structured data

From
Christian Couder <christian.couder@gmail.com>
Date
Dec 6, 2025, 21:02 UTC
Message-ID
<CAP8UFD3Ta5jdC7uU83iqT9+ZYEb2-CFkUWanAGQtD6fARmxG-Q@mail.gmail.com>
In-Reply-To
<aTR6Ky7Nq32uj4_5@air>
On Sat, Dec 6, 2025 at 7:48 PM Cedric Sodhi <manday@openmail.cc> wrote:
> Hello and thank you for the two suggestions. I've read up on them and came to the following understanding. But first, I would like to mention that by "data" that needs to be versioned, I was not referring to binary (opaque) data, but rather exactly the type of data which Git currently manages ("source code", in a sense); but in a structured form. Think text or sourcecode fragments in an SQL database.

Not sure it's what you are looking for but https://fossil-scm.org stores its content in an SQLite database.

Previous: Cedric SodhiNext: Simon Richter
Message 4 of 6 in “Git for structured data”
  1. Cedric SodhiDec 5, 2025
  2. René ScharfeDec 6, 2025
  3. Cedric SodhiDec 6, 2025
  4. Christian CouderDec 6, 2025
  5. Simon RichterDec 7, 2025
  6. Cedric SodhiDec 7, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.