News for hackers. Stuff that matters.

cannadayr

Re:Ask HN: Who wants to be hired? (March 2025) on Sunday March 09, 2025 @01:31PM (#43311451)
Location: California

Remote: Yes

Willing to relocate: Maybe

Technologies: BQN, Erlang, C

Résumé/CV: email me

Email: my username at gmail dot com

I'm pretty satisfied with gnu apl.
Re:Ask HN: Who wants to be hired? (April 2019) on Monday April 01, 2019 @06:56PM (#19549214)
Location: Boston, MA

Remote: Yes

Willing to relocate: No

Technologies: PHP, Bash, SQL, Javascript, Apache2, MariaDB, Postfix, Bind9, OpenVPN, Varnish, Debian, FreeBSD

Résumé/CV: https://github.com/cannadayr/resume/blob/master/resume.pdf

Email: [email protected]

Re:LiteTree: SQLite with Branches on Wednesday August 29, 2018 @03:52AM (#17866499)
Could you expand on the benefits to this?

Basically, git-sqlite already supports merges (see link above)

Re:LiteTree: SQLite with Branches on Wednesday August 29, 2018 @03:00AM (#17866264)
yup, np. shoot me an email sometime, looks like we're on a similar page.
Re:LiteTree: SQLite with Branches on Wednesday August 29, 2018 @02:48AM (#17866211)
Yes, I saw similar ideas ~ a year ago, & figured it was possible. It was just a matter of using sqlite's (excellent) sqldiff utility and wrapping a custom git diff driver. Took about an evening to get the proof-of-concept working and a little more fiddling for ease of use.

I don't have stress test results, but it should be similar to git. I think I remember getting it up to several hundred megabytes at one point and it was fine. I mostly use it for smaller sets of highly relational data that I want to track like I would source code.

By leveraging git & sqlite it lets me avoid writing a network sync implementation, architecture specific code, or patching any C code to recompile.

Re:LiteTree: SQLite with Branches on Wednesday August 29, 2018 @02:23AM (#17866101)
Neat. I'll have to compare this to my own implementation.

https://github.com/cannadayr/git-sqlite

Instead of storing the transactions as a separate lmdb commit, I decided to store the database in a git repository and expose the diffs using sqlite's sqldiff utility. This allowed my workflow to be almost unchanged and limits the dependencies to git, sqlite, sqldiff, & bash.

Re:JSON Changelog with SQLite on Monday August 27, 2018 @10:32PM (#17856210)
I solved this problem by wrapping sqldiff (included w/ sqlite src) as a custom git diff driver.

https://github.com/cannadayr/git-sqlite

If people are a little confused about what this does, it lets you track a sqlite database using git. If a change is detected to the database, the diff is the set of sql queries necessary to mutate the database from one state to the next.

I have found it to be extremely useful for certain problems.