StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1621444
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-10-25T17:17:52.357
FavoriteCount
0
LastActivityDate
2009-10-25T17:17:52.357
LastEditDate
LastEditorUserId
0
OwnerUserId
45435
ParentId
1621360
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
My vote is for going down the route of Model extends datastore. That seems most natural because in effect your model is an extension of the underlying datastore. However, you may want to use a Service design pattern to decouple the creation of the model object with the consumption of the resulting object. <pre><code>class Model { protected $_tablename == __CLASSNAME__; // or some derivative of the classname protected $_datastore; protected $_typeOfDataStore; function __construct( $type == 'mysql' ) { $this->_typeOfDataStore = $type; $this->bindToDataStore(); } function bindToDataStore( $ds ) { $this->_datastore = DataStoreFactory::buildDataStore( $this->_typeOfDataStore ); } } class DataStoreFactory { function buildDataStore( $type ) { switch ( $type ) { case 'flatfile' : return new FlatFileDataStore(); case 'mysql': return new MySQLDataStore(); } } } class DataStoreBase { function connect() { } function disconnect() { } function getData() { } // ... } class FlatFileDataStore extends DataStoreBase { } class MySQLDataStore extends DataStoreBase { function runQuery() { } } </code></pre> That's the construction part. When you need to create/implement a new model, you can simply extend the model: <pre><code>class Users extends Model { protected $_tablename = 'users'; protected $_typeOfDataStore = 'flatfile'; function getAllUsers() { return $this->runQuery( "SELECT * FROM " . $this->_tablename ); } } </code></pre> And in your controller: <pre><code>$usersModel = new Users(); $usersModel->getAllUsers(); </code></pre> The objection that you pointed out about the datastore being unable to use any of the Model's methods is a good constraint on the system. The model is a consumer of the datastore and thus the datastore should not be able to directly call the model object's functions. The model should maintain the control and make use of the datastore service whenever it needs to. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is the best practice for adding persistence to an MVC model?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPras
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. This table or related slice is empty.
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.