Discussion
pgit: What If Your Git History Was a SQL Database?
Zardoz84: Interesting... could be used to store multiple git repos and do a full text search across the multiple repos ?
smartmic: Of course, we can’t leave out a mention of Fossil here — the SCM system built by and for SQLite.https://fossil-scm.org/
killingtime74: I love it. I love having agents write SQL. It's very efficient use of context and it doesn't try to reinvent informal retrieval part of following the context.Did you find you needed to give agents the schema produced by this or they just query it themselves from postgres?
ImGajeed76: in theory yes. you just need to do the full text search across the databases. pgit doesnt support it but at the end its just postgres under the hood.
ImGajeed76: so most analyses already have a CLI function you can just call with parameters. for those that don't, in my case, the agent just looked at the --help of the commands and was able to perform the queries.
Fire-Dragon-DoL: Wouldn't duckdb be better suited for this? Forgive the stupid question. I just connected "csv as sql" to "git as sql" and duckdb comes to mind
ImGajeed76: I did actually look into writing the extension for duckdb. But similar to SQLite the extension possibilities are not great for what I needed. Though duckdb is a great database.
thunderbong: And fossil itself is an SQLite database!
Pay08: How much does it take advantage of being a DB underneath?
Pay08: This is incredibly neat and might actually become a part of my toolbox.
