Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, I'm a former svn user too, and now use git for all my projects.</p> <p>When using git, you should change the way of thinking from the client-server architecture that's used in svn. In svn, every change needs a connection with server. Using git, your repo is in the working directory. You don't need a connection for every repo action.</p> <p>Only use <code>git push</code> and <code>git pull</code> to synchronise with repo. Think of it like using rsync or any backup solution, to make two place have exactly same content. Just like you connect external backup hard disk, then make the content in it same with the content in your main. That's the usage of <code>git pull</code> and <code>git push</code>.</p> <p>If you just want to go back and forth the history, do it using <code>git checkout</code>. See the revision id using <code>git history</code>. If you're using Linux, use <code>gitk</code> to see the revision tree. In Windows, tortoise git can display it using revision graph.</p> <p>To get back to latest revision, use <code>git checkout master</code>. Before doing any command, always make yourself do <code>git status</code>. This command will display anything you need to know about current repo condition, and what action that you need to do to make it right. Before do <code>git pull</code> and <code>git push</code>, it's better to make sure that <code>git status</code> result is contain text <code>working directory clean</code>.</p> <p>If you need to revert a file to it's previous revision, you can do it with <code>git merge</code>. Before doing it to a file, test it first with <code>git diff</code>. Ex: <code>git diff rev1:rev2 filename</code>. It will print out any different between two revision. Change in rev1 will be replaced by the changes in rev2. So to do revert, rev2 will be the older than rev1. After you satisfy with the diff result, do it with <code>git merge</code>, just replace <code>diff</code> with <code>merge</code>, all other parameters stay the same.</p> <p>I hope this helps you. The main key is to see that your working dir is your repo. Understanding this will help you use git to it's full capability. Good luck.</p>
    singulars
    1. This table or related slice is empty.
    1. POGit: How to move back and forth between commits
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDonny Kurnia
    1. USDonny Kurnia
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGit: How to move back and forth between commits
      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. VTAcceptedByOriginator
    1. This table or related slice is empty.
 

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