Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I agree with T.E.D.'s answer in that I prefer to keep each project in a development directory. However, when I'm in the terminal looking at a bash listing I like to easily see three things:</p> <ol> <li>What type of repo is this --- Git, Mercurial, or Subversion</li> <li>Where is the pseudo-central repo stored --- Github.com, Bitbucket.org, Google Code, etc.</li> <li>Who owns the pseudo-central repo</li> </ol> <p>I've found that I can easily do this by using the following naming convention for my projects:</p> <pre><code>~/development/project.whatwhere.who </code></pre> <p>Since it is common when using Mercurial to clone a local project, I add one layer to the directory structure as:</p> <pre><code>~/development/project.whatwhere.who/project/ # Initial clone from remote repo ~/development/project.whatwhere.who/project.local.blah_descriptor/ # Local hg clone </code></pre> <p>The <code>whatwhere</code> convention that I use is as follows:</p> <ul> <li>github --- Git repo stored on github.com</li> <li>gitorious --- Git repo stored on gitorious.org </li> <li>git --- Git repo stored somewhere elsewhere</li> <li>gitsvn --- Subversion repo cloned using git-svn stored somewhere else</li> <li>hgbit --- Mercurial repo stored on bitbucket.org</li> <li>hg.gcode --- Mercurial repo stored on Google code</li> <li>hg --- Mercurial repo stored elsewhere</li> <li>svn.gcode --- Subversion repo stored on Google code</li> <li>svn.sforge --- Subversion repo stored on Sourceforge.net</li> <li>svn.work ---- Subversion repo stored on our company's svn server</li> <li>svn --- Subversion repo stored somewhere</li> </ul> <p>The <code>who</code> convention is simply the username of the desired person.</p> <p>Below are a few project examples, all residing in my <code>~/development/</code> directory:</p> <pre><code>fabric.github.bitprophet # Bitprophet's fabric project cloned from Github fabric.github.myusername # My fork of the fabric project from Github virtualenv.hgbit.ianb # Ianb's virtualenv project cloned from Bitbucket growl.hg.gcode # Growl project cloned from Google code ledgersmb.svn.sforge # LedgerSMB project checked out from Sourceforge coldfire.gitsvn # Coldfire Subversion project at work cloned using git-svn coldfire.svn # Coldfire Subversion project at work checked out with svn </code></pre> <p>To help organize your projects if you get too many, you may want to add a layer immediately beneath the <code>~/development</code> directory for organization. For example, you could have the following directories:</p> <pre><code>~/development/workprojects/ ~/development/opensrcprojects/ ~/development/personalprojects/ </code></pre> <p><em>Note</em>: I typically use Git for DVCS, so this answer is most likely slanted in that direction. </p>
    singulars
    1. This table or related slice is empty.
    1. POWhat directory structure makes sense for DVCS such as git?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMatthew Rankin
    1. USMatthew Rankin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. 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