Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>No need to stash.</p> <pre><code>git checkout -b new_branch_name </code></pre> <p>does not touch your local changes. It just creates the branch from the current HEAD and sets the HEAD there. So I guess that's what you want.</p> <p><strong>--- Edit to explain the result of checkout master ---</strong></p> <p>Are you confused because <code>checkout master</code> does not discard your changes?</p> <p>Since the changes are only local, git does not want you to lose them too easily. Upon changing branch, git does not overwrite your local changes. The result of your <code>checkout master</code> is:</p> <pre><code>M testing </code></pre> <p>, which means that your working files are not clean. git did change the HEAD, but did not overwrite your local files. That is why your last status still show your local changes, although you are on <code>master</code>.</p> <p>If you really want to discard the local changes, you have to force the checkout with <code>-f</code>.</p> <pre><code>git checkout master -f </code></pre> <p>Since your changes were never committed, you'd lose them.</p> <p>Try to get back to your branch, commit your changes, then checkout the master again.</p> <pre><code>git checkout new_branch git commit -a -m"edited" git checkout master git status </code></pre> <p>You should get a <code>M</code> message after the first checkout, but then not anymore after the <code>checkout master</code>, and <code>git status</code> should show no modified files.</p> <p><strong>--- Edit to clear up confusion about working directory (local files)---</strong></p> <p>In answer to your first comment, local changes are just... well, local. Git does not save them automatically, you must tell it to save them for later. If you make changes and do not explicitly commit or stash them, git will not version them. If you change HEAD (<code>checkout master</code>), the local changes are not overwritten since unsaved.</p>
    singulars
    1. This table or related slice is empty.
    1. POGit: Create a branch from unstaged/uncommitted changes on master
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGauthier
    1. USGauthier
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGit: Create a branch from unstaged/uncommitted changes on master
      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. COThis is how I always do it. It works exactly how you'd like it to.
      singulars
      1. PO
      1. USsynic
    2. COdude, I was missing this important point. I think I got why this happens and why git obviously can't ignore the changes (without forcing discard) if I don't commit them first. Thank you :D
      singulars
      1. PO
      1. USknoopx
    3. COThe confusing thing here is, that git’s man page states that `git checkout` “Updates files in the working tree to match the version in the index or the specified tree.”. That assumes your changes in your file system will be *GONE* afterwards. Without any chance to get them back. Even if you say they won’t, this still leaves a very bad feeling. I don’t trust this *at all*. Either the documentation is really bad or git’s default behavior is really dangerous. One should not have to trust on some “automagic” heuristic to detect that in this case you don’t want to lose your changes.
      singulars
      1. PO
      1. USEvi1M4chine
 

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