StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17295673
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-25T11:05:55.417
FavoriteCount
0
LastActivityDate
2013-06-25T11:05:55.417
LastEditDate
LastEditorUserId
0
OwnerUserId
2504013
ParentId
17295407
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Interfaces are used a lot because they are basically a blueprint of what your class should be able to do. For example, if you are writing a video game with characters, you can have an interface that holds all the methods that a character should have. For example <pre><code>public interface Character { public void doAction(); } </code></pre> And you have 2 characters, for example an ally and an enemy. <pre><code>public class Ally implements Character { public void doAction() { System.out.println("Defend"); } } public class Enemy implements Character { public void doAction() { System.out.println("Attack"); } } </code></pre> As you can see, both classes implement the interface, but they have different actions. Now you can create a character which implements your interface and have it perform its action. Depending on if it's an enemy or an ally, it'll perform a different action. <pre><code>public Character ally = new Ally(); public Character enemy = new Enemy(); </code></pre> And in your main program, you can create a method that accepts any object that implements your interface and have it perform it's action without knowing what kind of character it is. <pre><code>void characterDoAction(Character char) { char.doAction(); } </code></pre> If you would give ally to this method, the output would be: <pre><code>Defend </code></pre> If you would give enemy to this method, the output would be: <pre><code>Attack </code></pre> I hope this was a good enough example to help you understand the benefits of using interfaces.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POInterfaces in java
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJREN
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POInterfaces in 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
 VTAcceptedByOriginator
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.