Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I suppose you also read <a href="http://bazaar-vcs.org/BzrVsGit" rel="nofollow noreferrer">Bazaar vs. Git</a> article, but in the end, it all comes down to what <em>you</em> are looking for in term of "feature-rich code management".</p> <ul> <li><p>If, by code management, you are referring to <em>file</em> (and directories and renaming), go with Bazaar.</p></li> <li><p>If, by code management, you are looking at <em>content</em> management, Git is designed to manage just that (the staging area, for instance, allows you to record what current <em>content</em> you want to commit, even though you have already begun to make some large modification you end up not wanting to commit in the current branch)</p></li> </ul> <p>To be sure, re-read <a href="http://www.gelato.unsw.edu.au/archives/git/0504/0598.html" rel="nofollow noreferrer">Linus's original vision</a> for Git (back in April 2005). If you do agree with it, chances are Git will deliver what you want. In short:</p> <ul> <li>very simple model (blob-tree-commit-tag)</li> <li>no metadata added (for tracking renaming for instance)</li> <li>"strong" principles like: <blockquote> <ul> <li>"files" do not matter. The only thing that matters is how "content" moved in the tree</li> <li>You have an SCM that tracks what changed at the only level that really matters, namely the whole project. None of the information actually makes any sense at all at a smaller granularity, since by definition, a "project" depends on the other files, or it wouldn't be a project</li> </ul> </blockquote></li> </ul> <p>That "all project" notion is actually a strength an <strong><a href="https://stackoverflow.com/questions/984707/what-are-the-git-limits/984973#984973">a limit</a></strong> for Git in term of project management: you should not seek to put <em>everything</em> into <em>one</em> Git repository.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs it easier to manage code with Git or Bazaar?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USVonC
    1. USVonC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs it easier to manage code with Git or Bazaar?
      singulars
      1. PTQuestion
    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. COI'm not sure exactly what you mean by "file" versus "content". Bazaar already allows you to cherry-pick which files you want to commit into a branch, so I don't see what's gained by having a staging area. I don't see how you can *not* want file information to be tracked. For instance, in java, you really need to make sure all files have the right name, but it's still important no matter what the project is. When I think of "file" management, I think of sourcesafe & cvs's per-file versioning -- which bazaar is decidedly not.
      singulars
      1. PO
      1. USFryGuy
    2. CO@FryGuy: may be this answer might be a little more explicit: http://stackoverflow.com/questions/995636/popularity-of-git-mercurial-bazaar-vs-which-to-recommend/995799#995799
      singulars
      1. PO
      1. USVonC
    3. CO@FryGuy: git can detect changes across files. For example, say you have one file with two functions, and split it into two functions. You simply cannot track this using rename. Git and its rename detection can do this, and it works very well in my opinion (but is slow - very slow compared to other git operations, it can take up to 10-15 seconds for large files). I have an example here: http://cournape.wordpress.com/2009/05/12/why-people-should-stop-talking-about-git-speed/ To me, this + cheap branches are the two killer features of git compared to other tools.
      singulars
      1. PO
      1. USDavid Cournapeau
 

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