StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1963463
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-12-26T14:11:06.060
FavoriteCount
0
LastActivityDate
2013-05-03T18:49:57.157
LastEditDate
2013-05-03T18:49:57.157
LastEditorUserId
153049
OwnerUserId
153049
ParentId
1401323
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
First I think the title of the question isn't very clear, second I'm not entirely sure I understand what is being asked... In my opinion both the title and the post really should be edited to clean it up a bit. The post seems to contain 5 questions (if I might paraphrase): <ol> <li>How would one go about retrieving a dependent/parent object from an entity?</li> <li>Is <code>$person->getAddress()</code> a good way to retrieve the Address object for a person from the database?</li> <li>If this a good way to do it then what would the code look like?</li> <li>Is it okay to use the $domain object inside the getAddress method?</li> <li>Is it okay to keep relation information in the Person class?</li> </ol> As far as answers go: <ol> <li>In this case <code>$person->getAddress()</code> seems a good choice, you know, nice and descriptive. ;-)</li> <li>I don't see a problem: Person HAS A Address, to get that adress you ask the person object for is.</li> <li>The given code example seems to answer this, although it is a bit cluttered. I would've just made address a member object, but other than that it's mostly the same</li> <li>& 5. I'd say are mostly a matter of taste, priority and design-dependency. There really isn't a clean cut answer to this. Also, are we arguing semantics here or a real life scenario?</li> </ol> Some code to go along with answer Nr.3: (I couldn't get it to work properly within the list) <pre><code>class Person { protected $_domain = null; // domain is assigned when instantiated protected $_address; // object public function getAddress() { if (!isset($this->_address) ) { $this->_address = $this->_domain->getAddressForPerson($this); // assuming $this contains some sort of ID } return $this->_address; } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORetrieving dependent/parent from within domain entity method
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPotherca
UserOwnerUserId
1. USPotherca
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
2. 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.