StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8680710
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-30T14:56:35.613
FavoriteCount
0
LastActivityDate
2011-12-30T14:56:35.613
LastEditDate
LastEditorUserId
0
OwnerUserId
1123076
ParentId
8359676
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
You need to use Doctrine subclasses. Create a subclass for each namespace. This will let you reference a specific set of data by class name. <ul> <li>class Models_Price <ul> <li>subclass Models_Price_CD</li> <li>subclass Models_Price_DVD</li> <li>subclass Models_Price_Vinyl</li> </ul></li> </ul> In the Price class, you'll need to specify the following: <pre><code>public function setUp() { parent::setUp(); $this->setSubclasses( array( 'Price_CD' => array( 'media_namespace' => 'CD', ), 'Price_DVD' => array( 'media_namespace' => 'DVD', ), 'Price_Vinyl' => array( 'media_namespace' => 'Vinyl', ), ) ); } </code></pre> Let's make the assumption that ItemsOne uses namespace CD, ItemsTwo uses namespace DVD, and ItemsThree uses namespace Vinyl. For this situation, you would add the following relationship to each class: ItemsOne: <pre><code>$this->hasMany( 'Models_Price_CD as Prices', array( 'local' => 'id', 'foreign' => 'entity_id', ) ); </code></pre> ItemsTwo: <pre><code>$this->hasMany( 'Models_Price_DVD as Prices', array( 'local' => 'id', 'foreign' => 'entity_id', ) ); </code></pre> ItemsThree: <pre><code>$this->hasMany( 'Models_Price_Vinyl as Prices', array( 'local' => 'id', 'foreign' => 'entity_id', ) ); </code></pre> Now, each of the Prices relations will return only what you expect. Doctrine, seeing the subclass, will automatically namespace all the queries you perform on that table.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODoctrine Relationship on a namespaced table
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USkevin
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODoctrine Relationship on a namespaced table
 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.