StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6633897
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-09T09:20:13.203
FavoriteCount
0
LastActivityDate
2011-07-09T09:29:06.830
LastEditDate
2011-07-09T09:29:06.830
LastEditorUserId
589517
OwnerUserId
589517
ParentId
6633852
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Consider: <pre><code>String s1 = new String("hi"); String s2 = new String("hi"); System.out.println(s1 == s2); </code></pre> Will print <code>false</code>. However <pre><code>String s1 = "hi"; String s2 = "h1"; System.out.println(s1 == s2); </code></pre> Will print <code>true</code>. And <pre><code>String s1 = "hi"; String s2 = new String("hi"); System.out.println(s1 == s2); </code></pre> Will print <code>false</code>. This is why you should always use <code>String.equals</code> when comparing <code>String</code>s instead of <code>==</code>. But don't take my word for it... Check this excerpt from the Java Language Specification <a href="http://java.sun.com/docs/books/jls/third_edition/html/lexical.html#3.10.5" rel="nofollow">JLS 3.10</a>: <pre><code>Thus, the test program consisting of the compilation unit (§7.3): package testPackage; class Test { public static void main(String[] args) { String hello = "Hello", lo = "lo"; System.out.print((hello == "Hello") + " "); System.out.print((Other.hello == hello) + " "); System.out.print((other.Other.hello == hello) + " "); System.out.print((hello == ("Hel"+"lo")) + " "); System.out.print((hello == ("Hel"+lo)) + " "); System.out.println(hello == ("Hel"+lo).intern()); } } class Other { static String hello = "Hello"; } and the compilation unit: package other; public class Other { static String hello = "Hello"; } produces the output: true true true true false true This example illustrates six points: Literal strings within the same class (§8) in the same package (§7) represent references to the same String object (§4.3.1). Literal strings within different classes in the same package represent references to the same String object. Literal strings within different classes in different packages likewise represent references to the same String object. Strings computed by constant expressions (§15.28) are computed at compile time and then treated as if they were literals. Strings computed by concatenation at run time are newly created and therefore distinct. The result of explicitly interning a computed string is the same string as any pre-existing literal string with the same contents. </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow many object creates with new operator?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USchahuistle
UserOwnerUserId
1. USchahuistle
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
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.