StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20450320
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-12-08T05:42:52.523
FavoriteCount
0
LastActivityDate
2013-12-08T05:48:05.423
LastEditDate
2013-12-08T05:48:05.423
LastEditorUserId
877472
OwnerUserId
877472
ParentId
20450201
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
A couple of things to be corrected here, I'll attempt to address the ones I see. Firstly, the Java standard is to use lowercase names for variables. Makes it very difficult to read otherwise, as everything looks like a type name. Second, Never use <code>new String()</code> to create a new string Object. Java strings are immutable, and the JVM maintains a pool of strings used in the application. A string created with <code>new String()</code> will create a brand new copy from the string passed to that constructor, which is not drawn from that pool, but separately allocated (so in effect, unnecessarily allocating more memory for a string object which may already exist in the pool). Instead just pass the strings like <code>"bob"</code> and <code>"BobsWindshield"</code>. And finally, to answer the question directly, since your exact use-case is uncertain, your solution might not even need a Hash. You might be able to get away with using an <a href="http://docs.oracle.com/javase/7/docs/api/java/util/ArrayList.html" rel="nofollow"><code>ArrayList</code></a> instead, if you just care about plain simple storage of multiple objects of the same type. However, in order to use a <a href="http://docs.oracle.com/javase/7/docs/api/java/util/HashMap.html" rel="nofollow"><code>HashMap</code></a>, you need to keep in mind that a Hash / Map is a collection of Key-Value pairs. Your current implementation is essentially non-sensical if your intention is to store and index multiple <code>PlayerNames</code> objects. Do this instead: <pre><code>HashMap<String, PlayerNames> playerTempNeutral = new HashMap<String, PlayerNames>(); playerTempNeutral.put("Bob", new PlayerNames("Bob", "BobsWindshield"); playerTempNeutral.put("Ron", new PlayerNames("Ron", "RonsDoor"); </code></pre> In this example, "Bob" or "Ron" is the key, and the corresponding <code>PlayerNames</code> object is the value relating to that key. In order to get one of those objects from the collection, you simply do so using the key (or "index value", I guess you could call it): <pre><code>PlayerNames bob = playerTempNeutral.get("bob"); </code></pre> And of course, once you have your <code>bob</code> object, you can play with it as needed (ex: <code>bob.TagName</code>). I suspect this may not necessarily be your use-case, so you'll have to elaborate more if you need additional information. Hope this helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHashmap with class
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPaul Richter
UserOwnerUserId
1. USPaul Richter
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHashmap with class
 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

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.