StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>What you are trying to do is mix two design patterns: <a href="http://www.martinfowler.com/eaaCatalog/activeRecord.html">Active Record</a> and <a href="http://www.martinfowler.com/eaaCatalog/dataMapper.html">Data Mapper</a>.</p> <p>If you take a look at the Data Mapper pattern, you have the Mapper that accesses both the Model and the database. The Model is passive - usually does not call external resources (it's a POPO - Plain Old PHP Object).</p> <p>A solution for your issue is to inject the related information into the Model, thus keeping the Model only as a data structure.</p> <p>Here is a working scenario for an MVC application:</p> <p><strong>Controller</strong> - used for input validation & retrieving data from services</p> <pre><code><?php ... public function viewAction() { $id = (int) $this->params()->fromQuery('id'); $service = $this->getServiceLocator()->get('your-user-service-name'); $user = $service->getUser($id); ... } </code></pre> <p><strong>Service</strong> - used for executing the business logic; calls multiple Data Mappers</p> <pre><code><?php ... public function getUser($id) { // get user $mapper = $this->getServiceLocator()->get('your-user-mapper'); $user = $mapper->getUserById($id); // get articles $article_mapper = $this->getServiceLocator()->get('your-article-mapper'); $user->articles = $article_mapper->getArticlesByUser($id); return $user; } </code></pre> <p><strong>Data Mapper</strong> - used to manipulate one type of Domain entity - it should be composed with a tableGateway if you are accessing the database</p> <pre><code><?php ... public function getUserById($id) { $select = $this->tableGateway->getSql()->select(); $select = $select->where(array('id' => $value)); $row = $this->tableGateway->selectWith($select)->current(); return $row; } </code></pre> <p><strong>Domain Model</strong> - used for data representation</p> <pre><code><?php ... class User { public $name; // user name ... public $articles; // holds the user articles } </code></pre> <p>Advantages</p> <ol> <li>Passive Models are easy to read - understand the data structure and it's relations.</li> <li>Passive Models are easy to test - you don't need external dependencies.</li> <li>You separate the persistence layer from the Domain layer.</li> </ol> <p>Hope this helps!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload