Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From the <strong><em>theoretical</em></strong> point of view:</p> <ul> <li><strong>tags</strong> are symbolic names for a given <em>revision</em>. They always point to the same object (usually: to the same revision); they do not change.</li> <li><strong>branches</strong> are symbolic names for <em>line of development</em>. New commits are created on top of branch. The branch pointer naturally advances, pointing to newer and newer commits.</li> </ul> <hr> <p>From the <strong><em>technical</em></strong> point of view:</p> <ul> <li><strong>tags</strong> reside in <code>refs/tags/</code> namespace, and can point to <em>tag objects</em> (annotated and optionally GPG signed tags) or directly to <em>commit object</em> (less used lightweight tag for local names), or in very rare cases even to <em>tree object</em> or <em>blob object</em> (e.g. GPG signature).</li> <li><strong>branches</strong> reside in <code>refs/heads/</code> namespace, and can point only to <em>commit objects</em>. The <code>HEAD</code> pointer must refer to a branch (symbolic reference) or directly to a commit (detached HEAD or unnamed branch).</li> <li><strong>remote-tracking branches</strong> reside in <code>refs/remotes/&lt;remote&gt;/</code> namespace, and follow ordinary branches in remote repository <code>&lt;remote&gt;</code>.</li> </ul> <hr> <p>See also <a href="https://book.git-scm.com/docs/gitglossary" rel="noreferrer" title="gitglossary(7) - A GIT Glossary">gitglossary</a> manpage:</p> <blockquote> <p><strong>branch</strong> </p> <blockquote> <p>A "branch" is an active line of development. The most recent commit on a branch is referred to as the tip of that branch. The tip of the branch is referenced by a branch head, which moves forward as additional development is done on the branch. A single git repository can track an arbitrary number of branches, but your working tree is associated with just one of them (the "current" or "checked out" branch), and HEAD points to that branch.</p> </blockquote> <p><strong>tag</strong></p> <blockquote> <p>A ref pointing to a tag or commit object. In contrast to a head, a tag is not changed by a commit. Tags (not tag objects) are stored in <code>$GIT_DIR/refs/tags/</code>. [...]. A tag is most typically used to mark a particular point in the commit ancestry chain.</p> </blockquote> <p><strong>tag object</strong></p> <blockquote> <p>An object containing a ref pointing to another object, which can contain a message just like a commit object. It can also contain a (PGP) signature, in which case it is called a "signed tag object".</p> </blockquote> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POHow is a tag different from a branch in Git? Which should I use, here?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJakub Narębski
    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. COQuestion: if you treat a branch like a tag (that is, you create it, then never update it), is there any real difference?
      singulars
      1. PO
      1. USSteve Bennett
    2. CO@SteveBennett absolutely. There contains different informations (you can sign a tag, you can add a description to a branch). You can move a branch (so even if you never update it, you can still rebase it.). You cannot move a tag (it is linked to a specific commit). You can choose to push a branch. Tags aren't pushed by default. You should never use one for the other (unless you are really in an SVN mindset, in which case you need to "un-learn" that fast if you want to go on with git).
      singulars
      1. PO
      1. USVonC
    3. CO@SteveBennett: There is a difference how Git treats branches vs how it treat tags. Besides what VonC said, you cannot advance tag by mistake: "`git checkout <tag>`" would generate anonymous unnamed branch (so called 'detached HEAD') and select _state_ of tag. Creating a new commit does it on this unnamed branch, and does not change what tag points to.
      singulars
      1. PO
      1. USJakub Narębski
 

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