StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18910631
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-20T06:55:32.253
FavoriteCount
0
LastActivityDate
2013-09-20T06:55:32.253
LastEditDate
2017-05-23T11:51:15.297
LastEditorUserId
-1
OwnerUserId
1559219
ParentId
18910403
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<a href="https://stackoverflow.com/questions/10366904/within-the-containing-class-use-property-or-field">Answer by Oded</a> <ul> <li>When using Auto-Implemented properties, you don't have a choice - you must use the property, as you don't have any access to the generated field.</li> <li>If you property is not simple and does some extra work (validation, firing events etc...), you should call the property in order to centralize access and logic.</li> <li>If you have any other properties (meaning a simple property with no logic and a backing field) I would ask why are they not one of the above...</li> <li>With the example you have give, it makes little difference - it is more important to be consistent with how you use these and really boils down to personal aesthetics and coding style.</li> </ul> <a href="https://stackoverflow.com/questions/271318/should-you-access-a-variable-within-the-same-class-via-a-property">Answer by TheCodeJunkie</a> <ul> <li>One of the stronger argument for accessing local (class scope) variables through properties is that you add a level of abstraction in your class. If you change any logic concerning how that field is stored then the rest of your code will be left unaffected.</li> <li>For example you might change that from a local variable to a property of a child object, to a database call, to a webservice call, to a static property on a class and so on. When making the change it gives you a single point of change, the property, and you do not have to update the rest of your class since they all use the property.</li> <li>Also using the property enables you to apply business rules on the value of the property instead of having to enforce the same rule at each location where you'd directly access the field. Again, encapsulation</li> <li>With the introduction of automatic properties there's even less reason to explicitly have a local variable, unless you need to apply business rules on the get/set</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBetter using getter or class members when change/updates from inside my class
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USKurubaran
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. This table or related slice is empty.
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.