StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13740215
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-06T09:08:34.577
FavoriteCount
0
LastActivityDate
2012-12-06T09:08:34.577
LastEditDate
LastEditorUserId
0
OwnerUserId
1145086
ParentId
13690868
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
First it looks like you need to make a little bit more of a conceptual leap. With the data mapper pattern it helps to think in terms of objects instead of database tables. I found these two articles helpful when I needed to make the leap. <a href="http://phpmaster.com/building-a-domain-model/" rel="nofollow">http://phpmaster.com/building-a-domain-model/</a> <a href="http://phpmaster.com/integrating-the-data-mappers/" rel="nofollow">http://phpmaster.com/integrating-the-data-mappers/</a> That being said ZF 1 has some very useful tools for building a data mapper/domain model. The convention in ZF 1 is for each table you are working with to be accessible through the Zend_Db_Table api. The simplest way I've found is to just use the <a href="http://framework.zend.com/manual/1.12/en/zend.db.table.html#zend.db.table.defining" rel="nofollow">DbTable resource</a> for each table. You could also use the <code>Zend_Db::factory</code> or <code>new Zend_Db_Table('tableName')</code> or any other method that appeals to you. This example is based on a mp3 song track. <pre><code>//in effect this is the database adapter for database table 'track', This is $tableGateway used later. <?php class Application_Model_DbTable_Track extends Zend_Db_Table_Abstract { //name of database table, required to be set if name of class does not match name of table protected $_name = 'track'; //optional, column name of primary key protected $_primary = 'id'; } </code></pre> there are several ways to attach a table to the Db adapter and the Zend_Db_Table api, I just find this method simple to implement and it makes setting up a mapper simple as well. The mapper class is the bridge between the data source and your object (domain entity). The mapper interacts with the api for Zend_Db_Table in this example. A really important point to understand: when using classes that extend Zend_Db_Table_Abstract you have all the basic functionality of the Zend_Db component at your disposal. (find(),fetchall(), fetchRow(), select() ...) <pre><code><?php class Music_Model_Mapper_Track extends Model_Mapper_Abstract { //the mapper to access the songs artist object protected $artistMapper; //the mapper to access to songs album object protected $albumMapper; /** * accepts instance of Zend_Db_Table_Abstract * * @param Zend_Db_Table_Abstract $tableGateway */ public function __construct(Zend_Db_Table_Abstract $tableGateway = null) { //at this point I tend to hardcode $tablegateway but I don't have to $tableGateway = new Application_Model_DbTable_Track(); parent::__construct($tableGateway); //parent sets the $tablegateway variable and provides an abstract requirement //for createEntity(), which is the point of this class } /** * Creates concrete object of Music_Model_Track * * @param object $row * @return Music_Model_Track */ public function createEntity($row) { $data = array( 'id' => $row->id, 'filename' => $row->filename, 'format' => $row->format, 'genre' => $row->genre, 'hash' => $row->hash, 'path' => $row->path, 'playtime' => $row->playtime, 'title' => $row->title, 'track_number' => $row->track_number, 'album' => $row->album_id,//foriegn key 'artist' => $row->artist_id//foriegn key ); //instantiate new entity object return new Music_Model_Track($data); } /** * findById() is proxy for find() method and returns * an entity object. * * @param type $id * @return object Model_Entity_Abstract */ public function findById($id) { //instantiate the Zend_Db_Select object $select = $this->getGateway()->select(); $select->where('id = ?', $id); //retrieve one database table row $row = $this->getGateway()->fetchRow($select); //create one entity object Music_Model_Track $entity = $this->createEntity($row); //return one entity object Music_Model_Track return $entity; } //truncated } </code></pre> All that has gone before is for the express purpose of building the following object: <pre><code><?php class Music_Model_Track extends Model_Entity_Abstract { /** * $id, __set, __get and toArray() are implemented in the parent */ protected $album; protected $artist; protected $filename; protected $format; protected $genre; protected $hash; protected $path; protected $playtime; protected $title; protected $track_number; //artist and album mappers protected $albumMapper = null; protected $artistMapper = null; //these are the important accessors/mutators because they convert a foreign key //in the database table to an entity object. public function getAlbum() { //if the album object is already set, use it. if(!is_null($this->album) && $this->album instanceof Music_Model_Album) { return $this->album; } else { //else we make a new album object if(!$this->albumMapper) { $this->albumMapper = new Music_Model_Mapper_Album(); } //This is the album object we get from the id in our reference array. return $this->albumMapper->findById($this->getReferenceId('album')); } } //same as above only with the artist object. public function getArtist() { if(!is_null($this->artist) && $this->artist instanceof Music_Model_Artist) { return $this->artist; } else { if(!$this->artistMapper) { $this->artistMapper = new Music_Model_Mapper_Artist(); } return $this->artistMapper->findById($this->getReferenceId('artist')); } } //the setters record the foriegn keys recorded in the table row to an array, //this allows the album and artist objects to be loaded only when needed. public function setAlbum($album) { $this->setReferenceId('album', $album); return $this; } public function setArtist($artist) { $this->setReferenceId('artist', $artist); return $this; } //standard setter and getters truncated... } so when using the track object you would get album or artist info like: //this would be used in a controller most likely. $mapper = new Music_Model_Mapper_Track(); $track = $mapper->findById('1'); //all of the information contained in the album or artist object is //available to the track object. //echo album title, year or artist. This album object also contains the artist object //so the artist object would be available in two ways. echo $track->album->title; //or echo $track->artist->name; echo $track->album->artist->name; echo $track->getAlbum()->getArtist()->getName(); </code></pre> So what you really need to decide is how you want to structure your application. What I see as obvious may not be an option you wish to implement. A lot of the answers to your questions depend on exactly how these resources are to be used. I hope this helps you at least a little bit.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POZend Framework Model, Active Record pattern alternative
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRockyFord
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POZend Framework Model, Active Record pattern alternative
 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
 VTAcceptedByOriginator
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.