Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As you've asked the question, it's a very hard one. Let me start by giving some guidelines:<br> * People should be able to commit code all the time; if it is postponed several bugs or features are committed together which result with bigger changes, more conflicts and harder-to-find bugs (what about that commit broke some functionality?)<br> * Code in your main branch (trunk, team branch, whatever) should be well reviewed and tested, so that people will not interfere others.</p> <p>Failure in any of those will reduce your team productivity. So you need to come up with a method which allows both. I know of few non-perfect methods:</p> <p>Method 1: Code in main branch is always reviewed, hence review is done pre-commit, say using web-based code review tools like Malevich or ReviewBoard. It is important that after the review, exactly the reviewed changes are committed; hence people are not to change the reviewed files for some other feature in the same copy (they can however get another copy of the code). </p> <p>Method 2: Code in main branch is reviewed within 48 hours, after-commit. For this to work you need some mechanism to signal which files are code-review and which are not; we used SVN properties which contains the MD5 of the last reviewed file.</p> <p>Method 3: Code in main branch is always reviewed, review on the code is done in a branch used during development and the code is merged into the main branch only after the review. This sounds a little bit expensive as you never do changes on the main branch; but having a personal branch for developers in which they can make small fixes and scripting the merges would take the pain away.</p> <p>I've worked with all 3 methods and would personally choose (3). Good luck...</p>
    singulars
    1. This table or related slice is empty.
    1. POReview after commit vs review before commit?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USUri Cohen
    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
    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