Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've been using Mercurial both at work and in my own personal projects, and I am really happy with it. The advantages I see are:</p> <ol> <li><strong>Local version control.</strong> Sometimes I'm working on something, and I want to keep a version history on it, but I'm not ready to push it to the central repositories. With distributed VCS, I can just commit to my local repo until it's ready, without branching. That way, if other people make changes that I need, I can still get them and integrate them into my code. When I'm ready, I push it out to the servers.</li> <li><strong>Fewer merge conflicts.</strong> They still happen, but they seem to be less frequent, and are less of a risk, because all the code is checked in to my local repo, so even if I botch the merge, I can always back up and do it again.</li> <li><strong>Separate repos as branches.</strong> If I have a couple development vectors running at the same time, I can just make several clones of my repo and develop each feature independently. That way, if something gets scrapped or slipped, I don't have to pull pieces out. When they're ready to go, I just merge them together.</li> <li><strong>Speed.</strong> Mercurial is much faster to work with, mostly because most of your common operations are local.</li> </ol> <p>Of course, like any new system, there was some pain during the transition. You have to think about version control differently than you did when you were using SVN, but overall I think it's very much worth it.</p>
    singulars
    1. This table or related slice is empty.
    1. PODo you use distributed version control?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UStghw
    1. UStghw
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODo you use distributed version control?
      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. COHow does DVCS make fewer merge conflicts? And if you botch a merge in a regular VCS, can't you back up and do it again and check in that result.
      singulars
      1. PO
      1. USBrian Carlton
    2. COA DVCS makes merges easier to manage because each individual check-in tends to be smaller, as you just end up doing them locally when they're done. That gives the system a finer grained view of how things changed, making it easier for it to automate the merge. With a regular VCS, you can't back up and redo the merge in the same way because the state of your code was never recorded anywhere. It's not in any check in. So while you can get the repo's status back, your changes are likely to be lost. In a DVCS, you can commit your changes first, so both sides of the merge have full history.
      singulars
      1. PO
      1. UStghw
    3. COThe other way a DVCS avoids merge conflicts is that it has history of previous merges, so if a changeset was merged in already, the system does not try and merge it in again, whereas normal VCS systems like Subversion will include that changeset in the merge, increasing the chances of a conflict.
      singulars
      1. PO
      1. UStghw
 

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