If I recall correctly, the Fossil SCM uses SQLite under the covers for a lot of its stuff.
Obviously that's not surprising considering its creator, but hearing that was kind of the first time I had ever considered that you could translate something like Git semantics to a relational database.
I haven't played with Pgit...though I kind of think that I should now.
The sqlite project actually benefited from this dogfooding. Interestingly recursive CTEs [0] were added to sqlite due to wanting to trace commit history [1]
If I recall correctly, the Fossil SCM uses SQLite under the covers for a lot of its stuff.
Obviously that's not surprising considering its creator, but hearing that was kind of the first time I had ever considered that you could translate something like Git semantics to a relational database.
I haven't played with Pgit...though I kind of think that I should now.
The sqlite project actually benefited from this dogfooding. Interestingly recursive CTEs [0] were added to sqlite due to wanting to trace commit history [1]
[0] https://sqlite.org/lang_with.html#recursive_query_examples
[1] https://fossil-scm.org/forum/forumpost/5631123d66d96486 - My memory was roughly correct, the title of the discussion is 'Is it possible to see the entire history of a renamed file?'
On and of course, the discussion board is itself hosted in a sqlite file!
"If I recall correctly, the Fossil SCM uses SQLite under the covers for a lot of its stuff."
a fossil repository file is a .sqlite file yes
So SQLite is versioned in SQLite.
Makes sense, I haven't used the software in quite awhile.
Very cool
Technically correct title would be: s/Kernel into/Kernel Git History into/
Wow that has a very different meaning from what I thought.
Read the title and immediately thought "what a weird way to solve the performance loss with kernel 7..." The mind tricking itself :)
very nice, thank you for the effort spent to do this and the results