6 comments
If I recall correctly, the Fossil SCM uses SQLite under the covers for a lot of its stuff.<p>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.<p>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]<p>[0] <a href="https://sqlite.org/lang_with.html#recursive_query_examples" rel="nofollow">https://sqlite.org/lang_with.html#recursive_query_examples</a><p>[1] <a href="https://fossil-scm.org/forum/forumpost/5631123d66d96486" rel="nofollow">https://fossil-scm.org/forum/forumpost/5631123d66d96486</a> - My memory was roughly correct, the title of the discussion is 'Is it possible to see the entire history of a renamed file?'
"If I recall correctly, the Fossil SCM uses SQLite under the covers for a lot of its stuff."<p>a fossil repository file is a .sqlite file yes
Very cool
Technically correct title would be: s/Kernel into/Kernel Git History into/<p><pre><code> Pgit: I Imported the Linux Kernel Git History into PostgreSQL</code></pre>
Read the title and immediately thought "what a weird way to solve the performance loss with kernel 7..." The mind tricking itself :)
[dead]
very nice, thank you for the effort spent to do this and the results