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.
When you import a repository into Phabricator, it parses everything into a MySQL database. That's how it manages to support multiple version control systems seamlessly as well as providing a more straightforward path to implementing all of the web-based user interface around repo history.
Git was a (poor) imitation of the monotone DVCS, which stored its data in sqlite.
"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
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?'