StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
373830
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-12-17T06:49:23.543
FavoriteCount
0
LastActivityDate
2008-12-17T06:49:23.543
LastEditDate
LastEditorUserId
0
OwnerUserId
40513
ParentId
129773
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Null Objects Mapping to fields can be useful if you are implementing the <a href="http://en.wikipedia.org/wiki/Null_Object_pattern" rel="nofollow noreferrer">null object pattern</a> if your classes. As this cannot be performed (easily) when mapping to Properties. You end up having to store fake objects in the database. HQL I was unsure that with HQL queries you had to change the property names if you were using a field access approach. ie if you had <code><property name="FirstName" access="field.camelcase" /></code> I thought you could still write <code>"From Person where FirstName = :name";</code> as it would use the property name still. Further discussion on field strategies and Null object can be found <a href="http://forum.hibernate.org/viewtopic.php?t=980694&postdays=0&postorder=asc&start=15" rel="nofollow noreferrer">here</a>. Performance In relation to performance of field vs property on <a href="http://jaychapman.blogspot.com/2007/11/nhibernate-access-performance.html" rel="nofollow noreferrer">John Chapman's blog</a> It appears there isn't much of an issue in performance with small-midrange result sets. In summary, each approach has certain perks that may be useful depending on the scenario (field access allows readonly getters, no need for setters, property access works when nothing special is required from your poco and seems to be the defacto approach. etc)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONHibernate : map to fields or properties?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJafin
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.