StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POsvn client/server versions
primarykey
Id
1508466
data
AcceptedAnswerId
0
AnswerCount
4
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-10-02T09:07:00.670
FavoriteCount
0
LastActivityDate
2016-11-15T12:01:27.640
LastEditDate
2009-10-02T13:49:36.907
LastEditorUserId
135960
OwnerUserId
135960
ParentId
0
PostTypeId
1
Score
4
ViewCount
8564
LastEditorDisplayName
text
Body
If I understand correctly version of <a href="http://subversion.tigris.org/" rel="nofollow noreferrer">subversion</a> defines: <ul> <li>A structure repository on server</li> <li>A structure of working copy on client side</li> <li>API between client and server</li> </ul> Once we've install svn server, we don't touch/upgrade it. Things are more complex on client side. On client side (Windows) we currently use <a href="http://tortoisesvn.tigris.org/" rel="nofollow noreferrer">tortoisesvn</a>. It's version (correct me if I'm wrong) is corresponding to subversion version. Now, we're going port our application to Linux and therefore we consider using additional svn clients (svn command line utility, Eclipse plugin and some GUI frontend). Now the questions: <ol> <li>Is it possible several different clients will work on the same checkout code? If yes thus it means that I need carrefully pick up version of clients to be used, since each client expects a particular format/data be found in .svn directory?</li> <li>What is the relationship between version of server and client side? If for example server side is 1.4 and client is 1.6, thus it means that some 1.6 features won't work?</li> <li>Is it true that version of subversion client is not nessessary corresponding to the version of subverions, such as of <a href="http://rapidsvn.tigris.org/" rel="nofollow noreferrer">rapidsvn</a> as opposed to <a href="http://tortoisesvn.tigris.org/" rel="nofollow noreferrer">tortoisesvn</a>?</li> </ol>
Tags
<svn><version-control>
Title
svn client/server versions
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USdimba
UserOwnerUserId
1. USdimba
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POsvn client/server versions
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POsvn client/server versions
 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.