Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A Git query language

github.com

Post reply on HN
Print view View original

11–20 of 72 posts

Re: A Git query language

#11

Post by OJFord »

koolba wrote: post #4

This is pretty cool. Looks like it's local to the current repo which makes sense for most usage. Having something like this across a swathe of repos would be useful in different ways (ex: " What has Bob committed over all the repos for our projects that involves the string 'billing'? ". Minor off topic rant about the animated example: Who doesn't put a space at the end of their prompt after the $?! Ugh!

> Who doesn't put a space at the end of their prompt after the $?! Ugh!

I've always had mixed feelings about that. Resolved it now, by using '>', no space, which doesn't look cluttered since there's only ~1px right next to the first char entered.

Re: A Git query language

#12

Post by OJFord »

patkai wrote: post #5
taspeotis wrote: post #3

A Git query language (github.com) 10 points by bryanrasmussen 1 hour ago This ought to have (2014) in the title: Latest commit 49c1c17 on 22 Jun 2014.

That makes it even more interesting, I mean the fact that this or something similar didn't get traction. I often have an idea of what I would like to know about my repo, but don't want to start hacking the answer together.

https://github.com/gitql/gitql (last commit 12 days ago)

Re: A Git query language

#13

Post by jordigh »

masklinn wrote: post #10

Mercurial has a somewhat similar concept predating this (added circa 2010): revision sets ( https://www.selenic.com/mercurial/hg.1.html#revsets ) (for selection, and templates for selection but git has that built-in, kind-of, via log --format)

Mercurial's are completely general, though. Any Mercurial command that can accept a revision as an argument can also accept a revset expression. And templating isn't just for log, but for many other commands, such as grep or annotate (blame), and it's the same templating language for all of them. I also find hg templates a bit easier to read, because they're Djangoish/Jinjaish instead of being printf-ish like git's. Plus, you can save and compose Mercurial templates and revsets.

I was actually hoping that gitql had finally gotten inspiration from Mercurial and git would grow a general purpose query language, but it's read-only. :-(

Re: A Git query language

#14

Post by aardvark179 »

jordigh wrote: post #13
masklinn wrote: post #10

Mercurial has a somewhat similar concept predating this (added circa 2010): revision sets ( https://www.selenic.com/mercurial/hg.1.html#revsets ) (for selection, and templates for selection but git has that built-in, kind-of, via log --format)

Mercurial's are completely general, though. Any Mercurial command that can accept a revision as an argument can also accept a revset expression. And templating isn't just for log, but for many other commands, such as grep or annotate (blame), and it's the same templating language for all of them. I also find hg templates a bit easier to read, because they're Djangoish/Jinjaish instead of being printf-ish like git's.…

Revsets are a wonderful feature, and it's something I wish git had. Just being able to say I want to see what has changed between this branch head and its latest common ancestor with trunk is an incredibly simple and useful thing to be able to do.

Re: A Git query language

#15

Post by masklinn »

jordigh wrote: post #13
masklinn wrote: post #10

Mercurial has a somewhat similar concept predating this (added circa 2010): revision sets ( https://www.selenic.com/mercurial/hg.1.html#revsets ) (for selection, and templates for selection but git has that built-in, kind-of, via log --format)

Mercurial's are completely general, though. Any Mercurial command that can accept a revision as an argument can also accept a revset expression. And templating isn't just for log, but for many other commands, such as grep or annotate (blame), and it's the same templating language for all of them. I also find hg templates a bit easier to read, because they're Djangoish/Jinjaish instead of being printf-ish like git's.…

True all the way, but that may be a bit too much to chew on for people whose mind is already blown by gitql.

Re: A Git query language

#16

Post by bryanrasmussen »

taspeotis wrote: post #3

A Git query language (github.com) 10 points by bryanrasmussen 1 hour ago This ought to have (2014) in the title: Latest commit 49c1c17 on 22 Jun 2014.

sorry, didn't note the date, I just found it because I was needing something like it and was ready to start making it because I figured - better look if someone else did the work for me first.

Re: A Git query language

#17

Post by iagooar »

koolba wrote: post #4

This is pretty cool. Looks like it's local to the current repo which makes sense for most usage. Having something like this across a swathe of repos would be useful in different ways (ex: " What has Bob committed over all the repos for our projects that involves the string 'billing'? ". Minor off topic rant about the animated example: Who doesn't put a space at the end of their prompt after the $?! Ugh!

I agree. Since we work with microservices, we have +10 repo per project. Would be nice to be able to scan through all of them.

Re: A Git query language

#18

Post by icefox »

koolba wrote: post #4

This is pretty cool. Looks like it's local to the current repo which makes sense for most usage. Having something like this across a swathe of repos would be useful in different ways (ex: " What has Bob committed over all the repos for our projects that involves the string 'billing'? ". Minor off topic rant about the animated example: Who doesn't put a space at the end of their prompt after the $?! Ugh!

Git map would work for many cases

https://github.com/icefox/git-map

  Git map ql ...

Re: A Git query language

#19

Post by Erwin »

This might benefit from SQLite's Virtual tables: https://sqlite.org/vtab.html

With Virtual Tables you can expose any data source as a SQLite table -- then you can use every SQL feature that sqlite offers. You can just tell sqlite how to iterate through your data with a few functions, with an option to push down filtering information for efficiency.

You can also create your own aggregates, functions etc.

Here's an article where the author exposes redis as a table within sqlite: http://charlesleifer.com/blog/extending-sqlite-with-python/

Re: A Git query language

#20

Post by koolba »

icefox wrote: post #18
koolba wrote: post #4

This is pretty cool. Looks like it's local to the current repo which makes sense for most usage. Having something like this across a swathe of repos would be useful in different ways (ex: " What has Bob committed over all the repos for our projects that involves the string 'billing'? ". Minor off topic rant about the animated example: Who doesn't put a space at the end of their prompt after the $?! Ugh!

Git map would work for many cases https://github.com/icefox/git-map Git map ql ...

Nice. I can see a need for this as a lot of my projects are structured like that (multiple sibling repos). Running 'git map log --grep ...' seems particularly useful.

Quick eyeballing of the source, it does not handle whitespace in directory names properly. The for loop would treat them as separate, invalid, entries.

Of course I'd also fire someone on the spot that commits a project directory with whitespace in it...

Post reply on HN