StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10407925
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-05-02T04:54:29.947
FavoriteCount
0
LastActivityDate
2013-10-24T06:23:29.987
LastEditDate
2013-10-24T06:23:29.987
LastEditorUserId
2914365
OwnerUserId
1025201
ParentId
10407877
PostTypeId
2
Score
75
ViewCount
0
LastEditorDisplayName
text
Body
Multiple reasons: <ul> <li>If you allow field access like shape.x = 90</li> </ul> then you cannot add any logic in future to validate the data. say if x cannot be less than 100 you cannot do it, however if you had setters like <pre><code>public void setShapeValue(int shapeValue){ if(shapeValue < 100){ //do something here like throw exception. } } </code></pre> <ul> <li>You cannot add something like copy on write logic (see <a href="http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/CopyOnWriteArrayList.html" rel="noreferrer">CopyOnWriteArrayList</a>)</li> <li>Another reason is for accessing fields outside your class you will have to mark them public, protected or default, and thus you loose control. When data is very much internal to the class breaking <a href="http://en.wikipedia.org/wiki/Encapsulation_%28object-oriented_programming%29" rel="noreferrer">Encapsulation</a> and in general <a href="http://en.wikipedia.org/wiki/Object-oriented_programming" rel="noreferrer">OOPS</a> methodology.</li> </ul> Though for constants like <pre><code>public final String SOMETHING = "SOMETHING"; </code></pre> you will allow field access as they cannot be changed, for instance variable you will place them with getters, setters. <ul> <li>Another scenario is when you want your Class to be immutable, if you allow field access then you are breaking the immutability of your class since values can be changed. But if you carefully design your class with getters and no setters you keep the immutability intact. </li> </ul> Though in such cases you have to be careful in getter method to ensure you don't give out reference of objects(in case your class have object as instances). We can use the private variables in any package using getters and setters.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is the point of getters and setters?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USuser2914365
UserOwnerUserId
1. USmprabhat
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhat is the point of getters and setters?
 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
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.