StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15832743
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-04-05T11:27:26.373
FavoriteCount
0
LastActivityDate
2013-04-05T11:40:34.023
LastEditDate
2013-04-05T11:40:34.023
LastEditorUserId
592139
OwnerUserId
592139
ParentId
15832438
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
I suspect the simplest approach would be to create a trivial subclass of <code>TreeSet</code> that provides a two-argument constructor: <pre><code>public class MyTreeSet<T> extends TreeSet<T> { public MyTreeSet(Comparator<? super T> cmp, Collection<? extends T> coll) { super(cmp); addAll(coll); } } </code></pre> and use this as the type of your bean, passing both the comparator and the initial values as <code><constructor-arg></code> values. <pre><code><bean id="studentSet" class="com.example.MyTreeSet"> <constructor-arg index="0"> <bean class="com.example.MyComparator" /> </constructor-arg> <constructor-arg index="1"> <list> <ref bean="student1" /> <ref bean="student2" /> <ref bean="student3" /> </list> </constructor-arg> </bean> </code></pre> Or instead of a subclass of <code>TreeSet</code> you could write your own <code>FactoryBean</code>. To do it without writing any additional code you could use a second bean definition to do the adding <pre><code><bean id="studentSet" class="java.util.TreeSet"> <constructor-arg> <bean class="com.example.MyComparator" /> </constructor-arg> </bean> <bean id="studentSetFiller" factory-bean="studentSet" factory-method="addAll"> <constructor-arg> <list> <ref bean="student1" /> <ref bean="student2" /> <ref bean="student3" /> </list> </constructor-arg> </bean> </code></pre> but then any other bean into which you inject <code>studentSet</code> needs an additional <code>depends-on="studentSetFiller"</code> to make sure the set is populated before the target bean tries to use it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing Collections in Spring
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USIan Roberts
UserOwnerUserId
1. USIan Roberts
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing Collections in Spring
 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
 VTAcceptedByOriginator
CommentsPostId
1. COAwesome! Thanks a lot.
 singulars
 PostPostId
 PO
 UserUserId
 USMawia

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.