StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2839150
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-05-15T06:25:38.887
FavoriteCount
0
LastActivityDate
2010-05-15T06:40:05.533
LastEditDate
2017-05-23T12:34:50.693
LastEditorUserId
-1
OwnerUserId
276101
ParentId
2839137
PostTypeId
2
Score
32
ViewCount
0
LastEditorDisplayName
text
Body
Use <code>People implements Comparable<People></code> instead; this defines the natural ordering for <code>People</code>. A <code>Comparator<People></code> can also be defined in addition, but <code>People implements Comparator<People></code> is not the right way of doing things. The two overloads for <code>Collections.sort</code> are different: <ul> <li><code><T extends Comparable<? super T>> void sort(List<T> list)</code> <ul> <li>Sorts <code>Comparable</code> objects using their natural ordering</li> </ul></li> <li><code><T> void sort(List<T> list, Comparator<? super T> c)</code> <ul> <li>Sorts whatever using a compatible <code>Comparator</code></li> </ul></li> </ul> You're confusing the two by trying to sort a <code>Comparator</code> (which is again why it doesn't make sense that <code>Person implements Comparator<Person></code>). Again, to use <code>Collections.sort</code>, you need one of these to be true: <ul> <li>The type must be <code>Comparable</code> (use the 1-arg <code>sort</code>)</li> <li>A <code>Comparator</code> for the type must be provided (use the 2-args <code>sort</code>)</li> </ul> <h3>Related questions</h3> <ul> <li><a href="https://stackoverflow.com/questions/2266827/when-to-use-comparable-vs-comparator">When to use Comparable vs Comparator</a></li> <li><a href="https://stackoverflow.com/questions/1814095/sorting-an-arraylist-of-contacts">Sorting an ArrayList of Contacts</a></li> </ul> <hr> Also, do not use raw types in new code. Raw types are unsafe, and it's provided only for compatibility. That is, instead of this: <pre><code>ArrayList peps = new ArrayList(); // BAD!!! No generic safety! </code></pre> you should've used the typesafe generic declaration like this: <pre><code>List<People> peps = new ArrayList<People>(); // GOOD!!! </code></pre> You will then find that your code doesn't even compile!! That would be a good thing, because there IS something wrong with the code (<code>Person</code> does not <code>implements Comparable<Person></code>), but because you used raw type, the compiler didn't check for this, and instead you get a <code>ClassCastException</code> at run-time!!! This should convince you to always use typesafe generic types in new code. Always. <h3>See also</h3> <ul> <li><a href="https://stackoverflow.com/questions/2770321/what-is-a-raw-type-and-why-shouldnt-we-use-it">What is a raw type and why shouldn't we use it?</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to use Comparator in Java to sort
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USpolygenelubricants
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.