StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POData Mapper: Is my interpretation correct?
primarykey
Id
1970945
data
AcceptedAnswerId
1970988
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-12-28T18:54:26.420
FavoriteCount
4
LastActivityDate
2009-12-28T20:07:45.180
LastEditDate
LastEditorUserId
0
OwnerUserId
221023
ParentId
0
PostTypeId
1
Score
1
ViewCount
1227
LastEditorDisplayName
text
Body
I'm trying to confirm now, what I believe about the Data Mapper pattern. So here we go: Section A: A Data Mapper is a class which is used to create, update and delete objects of another Class. Example: A class called <code>Cat</code>, and a Data Mapper called <code>CatDataMapper</code>. And a database table called <code>cats</code>. But it could also be an xml file called <code>cats.xml</code>, or an hard-coded array called <code>cats</code>. The whole point of that Data Mapper is to free the Business Logic which uses the Cat class from thinking about "how to get an exisiting cat", or "how to save a cat", "where to save a cat". As a user of the Data Mapper it looks like a blackbox with well-defined methods like getCat(int id), saveCat(Cat catObject), deleteCat(Cat catObject), and so on. Section B: First I thought it would be clever if Cat inherits from CatDataMapper, because calling such functions then is a bit more convenient. For example, methods like catWithId(int id) could be static (class method) and return an instance of a Cat, initialized with data from anywhere. And when I work with a cat object in my code, I could simply call myCat->save(); to store it whereever the Data Mapper will store it (don't care where and how, the Data Mapper hides this complexity from the user). In conclusion, I'm a little bit confused now ;) Do you think that Section A is valid for the Data Mapper pattern? And if I would do it additionaly as described in Section B, would that be bad? Why?
Tags
<oop><datamapper>
Title
Data Mapper: Is my interpretation correct?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USopenfrog
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
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.