StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9220635
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2012-02-09T23:33:10.880
FavoriteCount
0
LastActivityDate
2014-12-16T14:57:00.863
LastEditDate
2014-12-16T14:57:00.863
LastEditorUserId
368630
OwnerUserId
368630
ParentId
9207680
PostTypeId
2
Score
54
ViewCount
0
LastEditorDisplayName
text
Body
You can use conditions using the <code><fail></code> task: <pre><code><fail message="Property &quot;foo&quot; needs to be set to a value"> <condition> <or> <equals arg1="${foo}" arg2=""/> <not> <isset property="foo"/> </not> </or> </condition> </code></pre> This is equivalent to saying <code>if (not set ${foo} or ${foo} = "")</code> is pseudocode. You have to read the XML conditions from the inside out. You could have used the <code><unless></code> clause on the <code><fail></code> task if you only cared whether or not the variable was set, and not whether it has an actual value. <pre><code><fail message="Property &quot;foo&quot; needs to be set" unless="foo"/> </code></pre> However, this won't fail if the property is set, but has no value. <hr> There's a trick that can make this simpler <pre><code>  <property name="foo" value=""/> <fail message="Property &quot;foo&quot; has no value"> <condition> <equals arg1="${foo}" arg2=""/> </condition> </fail> </code></pre> Remember that I can't reset a property! If <code>${foo}</code> already has a value, the <code><property></code> task above won't do anything. This way, I can eliminate the <code><isset></code> condition. It might be nice since you have three properties: <pre><code><property name="foo" value=""/> <property name="bar" value=""/> <property name="fubar" value=""/> <fail message="You broke the build, you dufus"> <condition> <or> <equals arg1="${foo}" arg2=""/> <equals arg1="${bar}" arg2=""/> <equals arg1="${fubar}" arg2=""/> </or> </condition> </fail> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to check if a property has value in Ant
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDavid W.
UserOwnerUserId
1. USDavid W.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to check if a property has value in Ant
 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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COTanks. Works great for me
 singulars
 PostPostId
 PO
 UserUserId
 USKK99
2. COIts nice to avoid nested ifs. Also with condition property & value can be set.
 singulars
 PostPostId
 PO
 UserUserId
 USuser1587504

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.