StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1433631
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-09-16T15:13:10.323
FavoriteCount
0
LastActivityDate
2012-11-21T18:43:48.740
LastEditDate
2012-11-21T18:43:48.740
LastEditorUserId
59087
OwnerUserId
94842
ParentId
1431315
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<h1>Build Process</h1> <ol> <li><code>build_info.properties</code> will be created during build in your project folder You could write all information about your build in this file. <ul> <li>Like build number, major and minor numbers of release, timestamp, and revision number.</li> </ul></li> <li>Your build script can modify these values how ever your want</li> <li>After the build was successfull commit the file 'build_info.properties' back to the repository</li> </ol> <h1>During Development</h1> <p>After first build the file build_info.properties will be placed in the repository. You can change and commit any number (major, minor, build numbers) by your self when ever you want, or increase it automatically during build like build.number in the example below. </p> <h1>svnant Example</h1> <p>Using svnant 1.3.0:</p> <pre><code><target name="checkout"> <echo>Checking out revision ${param_SubProjectSvnREV} of project: ${param_SubProjectSvnName}</echo> <svn username="${svnant.repository.user}" password="${svnant.repository.passwd}"> <checkout url="${svnant.latest.url}/${param_SubProjectSvnName}/" revision="${param_SubProjectSvnREV}" destPath="${all.projects.dir}/${param_SubProjectDirName}" /> <info target="${all.projects.dir}/${param_SubProjectDirName}" ></info> </svn> <propertyfile file="${all.projects.dir}/${param_SubProjectDirName}/build_info.properties" comment="Modify build numbers in a properties file."> <entry key="build.number" type="int" operation="+" value="1" pattern="00"/> <entry key="build.revision" type="string" value="${svn.info.rev}"/> <entry key="build.major.number" default="01"/> <entry key="build.minor.number" default="01"/> </propertyfile> </target> <target name="compile" depends="checkout"> <property file="${all.projects.dir}/${param_SubProjectDirName}/build_info.properties" /> <mkdir dir="${release.name}/${param_SubProjectDirName}/${build.major.number}.${build.minor.number}.${build.number}" />   </target> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBuild numbers: major.minor.revision
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDave Jarvis
UserOwnerUserId
1. USScrutator
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
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.