StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1302262
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-08-19T19:52:09.287
FavoriteCount
0
LastActivityDate
2016-08-12T18:12:02.817
LastEditDate
2016-08-12T18:12:02.817
LastEditorUserId
159447
OwnerUserId
159447
ParentId
1302230
PostTypeId
2
Score
9
ViewCount
0
LastEditorDisplayName
text
Body
With respect to software versioning (especially <a href="http://semver.org/" rel="nofollow noreferrer">semantic versioning</a>), patching will upgrade a software's patch version number, and updates upgrade their minor version number. For applications that follow semantic versioning (in <code>MAJOR.MINOR.PATCH</code> format), a patch is defined as: <blockquote> increment the [...] PATCH version when you make backwards-compatible bug fixes. </blockquote> In most cases, patches update the third number, the maintenance version. Updates update the minor version number. Furthermore, patches usually fix problems while maintaining compatibility, whereas updates can both fix problems as well as add new features which may not be compatible with previous versions. One may additionally append a build or revision number past the patch number: <pre><code>MAJOR.MINOR.PATCH or MAJOR.MINOR.PATCH.BUILD </code></pre> So a version number 2.1.3.089 is the second major version, first minor revision (so there has been one major update), third maintenance build (so three patches since version 2.1.0.X was released), and build 089 (no significance to builds/patches, can be thought of as additional metadata specifying a unique version ID/number). The <a href="http://en.wikipedia.org/wiki/Software_versioning" rel="nofollow noreferrer">Wikipedia article</a> on software versioning is an interesting read. The reason I specify the M.M.M.B style is that it is commonly used in Visual Studio during application development. In some cases, however, the last number (build) is omitted - for end users, rarely is this ever needed. It's mostly for development purposes only.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPatch vs. Upgrade
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBreakthrough
UserOwnerUserId
1. USBreakthrough
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPatch vs. Upgrade
 singulars
 PostTypePostTypeId
 PTQuestion
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. 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.