StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5512722
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-04-01T11:28:16.367
FavoriteCount
0
LastActivityDate
2011-04-01T11:43:54.053
LastEditDate
2011-04-01T11:43:54.053
LastEditorUserId
574185
OwnerUserId
574185
ParentId
5499915
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
A colleague and I came up with the answer by looking through the <code><zip></code> and <code><concat></code> source. There are really two answers: <ol> <li><code><concat></code>'s implementation of the <code>ResourceCollection</code> interface is odd, but we understand why.</li> <li>There's a way around that.</li> </ol> For #1, while <code><concat></code> is a <code>ResourceCollection</code> (like <code>FileSet</code>), under the hood it returns as the name of single <code>Resource</code> it contains a hard-coded value: <pre><code>"concat (" + String.valueOf(c) + ")"; </code></pre> Look familiar? The name of resources is normally ignored--except by <code><zip></code> and its related tasks, which uses the resource name as the <code>ZipEntry</code> name. Since <code><concat></code> returns the odd-looking name, that's what we get in the zip file. I haven't quite figured out why I get multiple entries, but it doesn't matter: the observation leads to a convoluted solution. Since I know the name of the <code>ZipEntry</code> I want to create, I can use a <code><mapper></code> to give the <code><concat></code> resource a name. Here's what I came up with in all its glory: <pre><code><zip destfile="target/distribution.zip"> <fileset dir="."> <exclude name="target/**" /> <exclude name="CHANGES.txt" /> </fileset> <mappedresources> <concat> <fileset file="CHANGES.txt" /> <filterchain> <expandproperties /> </filterchain> </concat> <mergemapper to="CHANGES.txt" /> </mappedresources> </zip> </code></pre> As my colleague says "In Ant every problem can be solved using a mapper." This only works for Ant 1.8+ because <code><mappedresources></code> was added in that release. I'm going to post some comments to the Ant mailing list and suggest a couple of enhancements: <ol> <li>Allow a resource name to be specified as an attribute on <code><concat></code> when it's being used as a <code>ResourceCollection</code>.</li> <li>Throw an exception (and don't create a synthetic value) if <code>getName()</code> is called without having a value specified.</li> <li>Finally, though not directly related, I do wish <code><expandproperties></code> could take a <code><propertyset></code> so I can control which properties get substituted.</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POconcat as resource collection in zip not working?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRichard Steele
UserOwnerUserId
1. USRichard Steele
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POconcat as resource collection in zip not working?
 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
 VTAcceptedByOriginator
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.