StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2164631
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-01-29T19:37:04.493
FavoriteCount
0
LastActivityDate
2010-01-29T19:37:04.493
LastEditDate
LastEditorUserId
0
OwnerUserId
16797
ParentId
2163739
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
See the difference, between include and import in the Ant manual. Also use macrodefs. I've slightly adapted your example, you'll need several files: build.xml, common.xml and macrodef_project_setup.xml build.xml <pre><code><?xml version="1.0"?> <project name="Ant_Test" basedir="." default="init"> <import file="common.xml"/>  <target name="common.init"/> <target name="setup" depends="init"/> <target name="do.several" depends="common.setup"> <echo message="In do.several, calling do.first" /> <antcall target="do.first" /> <echo message="In do.several, calling do.second" /> <antcall target="do.second" /> </target> <target name="do.first" depends="common.setup"> <echo message="In do.first" /> </target> <target name="do.second" depends="common.setup"> <echo message="In do.second" /> </target> </project> </code></pre> common.xml <pre><code><?xml version="1.0"?> <project name="common"> <target name="init"> <project_setup option="Stack.Over.Flow"/> </target> <target name="setup"> </target> <import file="macrodef_project_setup.xml"/> </project> </code></pre> macrodef <pre><code><?xml version="1.0"?> <project name="project_setup" basedir="."> <macrodef name="project_setup"> <attribute name="option" default=""/> <sequential>  <echo>THIS IS MY SETUP OPTION: @{option}</echo> </sequential> </macrodef> </project> </code></pre> Output: <pre><code>ant -p Buildfile: build.xml Main targets: Other targets: common.setup do.first do.second do.several init setup Default target: init </code></pre> Default target is now init. <pre><code>ant Buildfile: build.xml Ant_Test.init: [echo] In setup initialization [echo] THIS IS MY SETUP OPTION: Stack.Over.Flow </code></pre> But you could still use ant setup. <pre><code>ant setup Buildfile: build.xml Ant_Test.init: [echo] In setup initialization [echo] THIS IS MY SETUP OPTION: Stack.Over.Flow </code></pre> Run it with do.several. <pre><code>ant do.several Buildfile: build.xml Ant_Test.init: [echo] In setup initialization [echo] THIS IS MY SETUP OPTION: Stack.Over.Flow Ant_Test.do.several: [echo] In do.several, calling do.first Ant_Test.do.first: [echo] In do.first [echo] In do.several, calling do.second Ant_Test.do.second: [echo] In do.second </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs there a way to guarantee that an ant dependency is run only once?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USuser16797
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. COThanks, Dean. That's very impressive. I will indeed look at include, import, and macrodef in more detail. Thanks.
 singulars
 PostPostId
 PO
 UserUserId
 USCPerkins

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.