Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I thought this would be a generally useful thing to have, so I wrote up a little perl script to do it:</p> <pre class="lang-perl prettyprint-override"><code>#!/usr/bin/perl -w use strict; my @commits; my %trees; my $blob; sub blob_in_tree { my $tree = $_[0]; if (defined $trees{$tree}) { return $trees{$tree}; } my $r = 0; open(my $f, "git cat-file -p $tree|") or die $!; while (&lt;$f&gt;) { if (/^\d+ blob (\w+)/ &amp;&amp; $1 eq $blob) { $r = 1; } elsif (/^\d+ tree (\w+)/) { $r = blob_in_tree($1); } last if $r; } close($f); $trees{$tree} = $r; return $r; } sub handle_commit { my $commit = $_[0]; open(my $f, "git cat-file commit $commit|") or die $!; my $tree = &lt;$f&gt;; die unless $tree =~ /^tree (\w+)$/; if (blob_in_tree($1)) { print "$commit\n"; } while (1) { my $parent = &lt;$f&gt;; last unless $parent =~ /^parent (\w+)$/; push @commits, $1; } close($f); } if (!@ARGV) { print STDERR "Usage: git-find-blob blob [head ...]\n"; exit 1; } $blob = $ARGV[0]; if (@ARGV &gt; 1) { foreach (@ARGV) { handle_commit($_); } } else { handle_commit("HEAD"); } while (@commits) { handle_commit(pop @commits); } </code></pre> <p>I'll put this up on github when I get home this evening.</p> <p>Update: It looks like somebody <a href="http://github.com/jwiegley/git-scripts/tree/master/git-find-blob" rel="nofollow noreferrer">already did this</a>. That one uses the same general idea but the details are different and the implementation is <em>much</em> shorter. I don't know which would be faster but performance is probably not a concern here!</p> <p>Update 2: For what it's worth, my implementation is orders of magnitude faster, especially for a large repository. That <code>git ls-tree -r</code> really hurts.</p> <p>Update 3: I should note that my performance comments above apply to the implementation I linked above in the first Update. <a href="https://stackoverflow.com/questions/223678/git-which-commit-has-this-blob#223890">Aristotle's implementation</a> performs comparably to mine. More details in the comments for those who are curious.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhich commit has this blob?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USGreg Hewgill
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHmm, how can it be *that* much faster? You’re walking the tree anyway, aren’t you? What work does git-ls-tree do that you avoid? (NB.: grep will bail on first match, SIGPIPE’ing the git-ls-tree.) When I tried it, I had to Ctrl-C your script after 30 seconds; mine was done in 4.
      singulars
      1. PO
      1. USAristotle Pagaltzis
    2. COMy script caches the results of subtrees in the %trees hash, so it doesn't have to keep searching subtrees that haven't changed.
      singulars
      1. PO
      1. USGreg Hewgill
    3. COActually, I was trying the implementation I found on github that I linked to. Yours is faster in some cases, but it depends highly on whether the file you're looking for is at the beginning or end of the ls-tree list. My repository has 9574 files in it right now.
      singulars
      1. PO
      1. USGreg Hewgill
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload