Databases
StackOverflow2013
Usersdbo
USFace
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USFace
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COYour layout seems to resemble the space partitioning of the branches, not the time partitioning. Does it mean that there is a release branch where dev, test and main branches away from? Or does it just mean that you grouped those 3 branches under the "releases" umbrella?
      singulars
      1. POMoving from TFS to Git or Mercurial strategy?
      1. USFace
    2. CO@HighCommander4: if you come from hg's native branch mechanism - that really is nothing more than node coloring with benefits - it is easy to misunderstand the need for an equivalent of Git's revision range specifier. With named branches, displaying the set of commits belonging to a branch is very easy, as the divergence point simply is the first commit having the appropriate "color". Git OTOH can't distinguish common changesets of two topological branches, because it only uses pointers to the heads of both lines. Thus there is the need to use set-functions with given ordering to list them.
      singulars
      1. PO
      1. USFace
    3. CO@HighCommander4: LazyBadger's approach would fail your requirement of not having to mark the divergence point, because Mercurial's x..y simply don't work if x is not an ancestor of y. The reason for this is right there in "hg help revsets". It states that x::y (or x..y) is `A DAG range, meaning all changesets that are descendants of x and ancestors of y, including x and y themselves. If the first endpoint is left out, this is equivalent to "ancestors(y)", if the second is left out it is equivalent to "descendants(x)".` This is clearly not the same as Git's specification mentioned in my answer.
      singulars
      1. PO
      1. USFace
 

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