Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The <code>Feature branches</code> option of Bazaar Explorer creates a so-called <strong>Shared Repository</strong> and a single branch called <code>trunk</code> inside it (called a <strong>Repository Tree</strong>). In your example:</p> <ul> <li><code>_Source Control</code> == <strong>Shared Repository</strong></li> <li><code>_Source Control/trunk</code> == <strong>Repository Tree</strong></li> </ul> <p>The idea is that in this setup you can create multiple branches next to <code>trunk</code>, and they will store revision data efficiently, by sharing stuff in the shared repository, to put it in a nutshell.</p> <p>If you are a beginner, then don't worry about branches. At some point it will probably naturally come to you. For example you realize you want to do something experimental but you don't want to mess up your trunk. The obvious solution will be to create a branch.</p> <p>Now about your workflow:</p> <ul> <li><p>I think you can use the <code>bzr upload</code> plugin for both the staging site and the live site.</p></li> <li><p>To roll back your live site to a previous version, use <code>bzr upload -rREV --overwrite</code> where <code>REV</code> is the revision you want to rollback to. Using the <code>--overwrite</code> there looks dirty, and it probably is. But that's the only way it works for me, I think it's a bug in my version of the plugin (<code>1.0.1dev</code>), I suggest to try first without that flag.</p></li> <li><p>To fix the bug, no need to roll back locally, just fix the bug and confirm it, then upload again with <code>bzr upload</code> without the other flags to bring the website up to the latest version.</p></li> </ul> <p>There are many ways of working with Bazaar. You can implement a beautiful and sophisticated workflow, or use this somewhat dirty but simple and easy to understand workflow. Let me know if you have further problems.</p> <p>And no, you don't need <code>checkout</code> in the setup you described.</p>
    singulars
    1. This table or related slice is empty.
    1. POBazaar: Do I need branches?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USjanos
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBazaar: Do I need branches?
      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. COVery helpful answer. I like the idea of your solution for reverting the live site to previous version using bzr-upload, I hadn't even thought it could be used to upload an earlier revision. That keeps things simple as it doesn't involve spawning off any new branches. I'm still not sure though about using bzr-upload to update the staging site as I tend to do lots of incremental updates of just 1 or 2 files when I'm working on something and I may also have 1 or 2 other files in a broken state at the same time so FTPing individual files seems better to me - at least that's what I'm used to.
      singulars
      1. PO
      1. USAidanCurran
    2. COIf you want to update just 1-2 files via FTP, you have to select the individual files manually, whereas `bzr upload` is a just one simple command, so I don't see how FTP would be easier. Using `bzr upload` consistently will also ensure consistency between your local env and the beta site. Btw, if you have ssh access to your sites then use bzr+ssh:// style URLs instead of ftp:// for more efficient (and secure) transfers
      singulars
      1. PO
      1. USjanos
    3. COFileZilla is what I'm used to but I might try it out for uploading to staging and see how it goes. Am i correct to assume i dont need to do a commit prior to calling `bzr upload` to upload the latest modified files?
      singulars
      1. PO
      1. USAidanCurran
 

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