StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4619124
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-01-06T19:46:02.410
FavoriteCount
0
LastActivityDate
2011-01-06T19:46:02.410
LastEditDate
LastEditorUserId
0
OwnerUserId
565342
ParentId
4561378
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
My advise will be to put in the same repository projects with the same lifecycle. Let's take your A scenario. We have: <ol> <li>Shared Class Library project (which is for lots of different solutions)</li> <li>Another Class Library project (which is only for this solution)</li> <li>Web Application project (which main part of this solution)</li> <li>Shared Web Service project (which also serves for different solutions)</li> </ol> That'll make one repository for 2 & 3 which are different projects of the same solution (hence with the same life cycle): <pre><code>/solution-A/trunk/ClassLib /solution-A/trunk/WebApp /solution-A/tags/1.0.0/ClassLib /solution-A/tags/1.0.0/WebApp </code></pre> And one repository for 1 & another for 4 assuming that they have different life cycles. <pre><code>/library-A/trunk/ShClassLib /library-A/tags/1.0.0/ShClassLib /library-B/trunk/ShWebService /library-B/tags/1.0.0/ShWebService </code></pre> Now depending on the subject on which a developer is working he can check out either the trunk, a tag (read only) or a branch. For instance a developer working on the solution using released libraries will check out the trunk of the solution and the right tags for the libraries. The same one requiring the next versions of the libraries will check out the trunk (or a branch) for the libraries, etc. Of course it'll be probably better to have a build/release system able to deliver binary releases for the libraries as well as nightly builds. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCode management in different projects with different svn repositories
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USgabuzo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
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.