StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2109840
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
12
CommunityOwnedDate
2010-01-21T15:23:44.173
CreationDate
2010-01-21T14:20:29.653
FavoriteCount
0
LastActivityDate
2010-01-21T20:09:29.607
LastEditDate
2017-05-23T12:00:14.263
LastEditorUserId
-1
OwnerUserId
73070
ParentId
2109807
PostTypeId
2
Score
63
ViewCount
0
LastEditorDisplayName
text
Body
Well, while C# and Java are superficially alike there are a number of small differences that might bite you. Generally I think the opposite direction—going from Java to C#—is less problematic. This is mainly due to C# being a more complex language so you might find many simplifications from common Java patterns but the other way around might be a little painful. Things to look out for (partial list, not guaranteed to be exhaustive): <ul> <li>Different ... <ul> <li>Naming conventions. In Java only type names start with a capital letter (i. e. PascalCase), everything else uses camelCase. Not very hard to adhere to, though. Also interfaces generally don't start with <code>I</code>. On the other hand you have to implement them with a different keyword. Doesn't really help in the middle of the code, though.</li> <li>Class library :-) While obvious, this has been the thing I spent most time on when learning a language. When dealing with a known paradigm the syntax differences are quickly sorted out, but getting to know the standard library / class library / framework takes some time in some cases :-)</li> <li>Patterns. Well, not quite, it's still the same stuff. But C# supports some patterns at the language level, while you still have to implement them yourself in Java. No events, but the Observer pattern (very prevalent in Swing—whenever you see a Listener, you know what to do :-))</li> <li>Exception handling. Java has so-called checked exceptions which means that an exception must either be caught or declared upwards. Usually this means that you have <pre><code>catch (SomeException ex) { ex.printStackTrace(); } </code></pre> pretty often in your code1 :-)</li> <li>Types. While .NET has normal objects and value types, they both are objects and support methods, properties, &c. Java has a dichotomy of primitive types, such as <code>int</code>, <code>float</code>, <code>char</code>, &c. and classes such as <code>String</code>. Doesn't matter much since they implemented auto-boxing, but sometimes it's still annoying to wrap <code>int</code> in <code>Integer</code>.</li> <li>Polymorphism: All Java methods are <code>virtual</code> by default whereas c# methods are not.</li> </ul></li> <li>Minor syntactic differences. <ul> <li><code>foreach (a in b)</code> → <code>for (a : b)</code></li> <li>Different access keywords. Things like <code>internal</code> and <code>protected internal</code> don't exist. But unqualified members are visible to other classes in the same package (sort of <code>internal</code>, but then again not quite).</li> <li>String comparison isn't done with <code>==</code> in Java. You have to use <code>.equals()</code>. While in C# <code>==</code> on strings is value equality, in Java <code>==</code> is always reference equality.</li> </ul></li> <li>No ... <ul> <li>Properties. In Java this is generally done with the <code>Foo getFoo()</code>/<code>void setFoo(Foo foo)</code> pattern which C# generates silently behind your back when using properties but you have to do it explicitly in Java. Generally, to keep the language itself simpler many things in Java are just conventions. Still, most of the time you're better off adhering to them :-)</li> <li>Operator overloading. Deemed a hazard to the righteous programmer they weren't implemented for fear of abuse. Don't need them too often anyway, not even in C#, but sometimes they are nice and then you're missing something.</li> <li>Indexers. You always have to access list items through <code>myList.get(5)</code> instead of the array-like syntax <code>myList[5]</code>. Just a mild inconvenience, though.</li> <li>LINQ (though there exist implementations2 but it's not as nicely integrated), or lambda functions3 (no delegates anyway, but anonymous classes), extension methods, or partial classes (yes, that's a painful one when dealing with Swing, unless you're very disciplined), and a few more things.</li> <li>Multidimensional arrays. You can use jagged arrays (arrays of arrays), buttrue multidimensionality isn't there.</li> </ul></li> <li>Generics are compile-time only, at runtime only <code>Object</code>s remain. Also wildcards in generics can be hard to resolve sometimes when the compiler complains about all of the four <code>?</code> in your generics having different types. (Though to be fair: That was a case where I would have needed type information at runtime anyway so I reverted back to <code>Object</code>s).</li> </ul> General advice: Grab a friend with Java experience and let him glance over your code. While he probably can't tell you everything you should take care of when you directly ask him that question, he can spot strange things in code just fine and notify you of that. This has greatly helped me learning Java (although I learned Java first and then C#, so it might be different). <hr> 1 Yes, I know many catch blocks look different, but still, this is probably the archetypical one and <a href="http://googletesting.blogspot.com/2009/09/checked-exceptions-i-love-you-but-you.html" rel="noreferrer">not even that rare</a>. 2 <a href="http://xircles.codehaus.org/projects/quaere" rel="noreferrer">Quaere</a>, <a href="http://code.google.com/p/jaque/" rel="noreferrer">JaQue</a>, <a href="http://h2database.com/html/jaqu.html" rel="noreferrer">JaQu</a>, <a href="http://source.mysema.com/display/querydsl/Querydsl" rel="noreferrer">Querydsl</a> 3 There's <a href="http://code.google.com/p/lambdaj/" rel="noreferrer">lambdaj</a>, though. Thanks for pointing that out, <a href="https://stackoverflow.com/users/44523/esko">Esko</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGoing from C# to Java
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USJoey
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGoing from C# to Java
 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
 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.