cannadayr

4 ms·

1.
by cannadayr 2y ago
Location: California Remote: Yes Willing to relocate: Maybe Technologies: BQN, Erlang, C Résumé/CV: email me Email: my username at gmail dot com
2.
by cannadayr 6y ago
I'm pretty satisfied with gnu apl.
3.
by cannadayr 7y ago
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&
4.
by cannadayr 8y ago
Could you expand on the benefits to this? Basically, git-sqlite already supports merges (see link above)
5.
by cannadayr 8y ago
yup, np. shoot me an email sometime, looks like we're on a similar page.
6.
by cannadayr 8y ago
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 a
7.
by cannadayr 8y ago
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
8.
by cannadayr 8y ago
I solved this problem by wrapping sqldiff (included w/ sqlite src) as a custom git diff driver. https://github.com/cannadayr/git-sqlite
9.
by cannadayr 8y ago
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
10.
Show HN: Git-sqlite, a custom diff and merge driver for sqlite(github.com)
6 points by cannadayr 8y ago|1 comments