StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10663707
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-05-19T08:40:44.773
FavoriteCount
0
LastActivityDate
2012-05-19T08:40:44.773
LastEditDate
LastEditorUserId
0
OwnerUserId
1145086
ParentId
10660967
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
ZF 1.x is not really modular and I think modules in ZF 1.x are a bit of a misnomer. They are more like domain libraries in my opinion. With that being said, I look at code separation like this (pure opinion). <ul> <li>Any code that I expect to be reused or reusable in another project I put in the library. eg. View helpers, action helpers, abstract model classes, base models, plugins etc...</li> <li>Any code that is application specific and will be used universally in the app I put in the application level directories. This is stuff like concrete data mappers, DbTable Models (I don't use Doctrine), forms and layouts...</li> <li>Any code that belongs specifically to a module(domain) and will not or cannot be used anywhere else I put in module level directories. This includes stuff like special view and action helpers, one of forms, and mostly it's where I put my domain(entity) models.</li> </ul> To illustrate this I'll present an example (personal namespace omitted): I have a module named music in my application, this module has a database table named 'music'. so these are the files I might have to use this Db table in my module. <pre><code>//The DbTable model application /models /DbTable /Music.php //extends Zend_Db_Table_Abstract </code></pre> To use that DbTable model I build a mapper that uses 2 files <pre><code>//Base mapper class library /Application /Model /Mapper.php //The concrete mapper application /modules /models /MusicMapper.php //extends Namespace_Application_Model_Mapper </code></pre> and to use that mapper I would have a domain model which is made up of 2 files, a base entity class and concrete entity class. <pre><code>//Base entity class library /Application /Model /Entity.php //and the concrete entity class application /modules /models /Music.php //extends Namespace_Application_Model_Entity </code></pre> I feel that organizing my files and classes this way keeps the code as DRY as possible without getting too confusing and scattered. I hope this helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POModel that is used in several modules. Where should it be located?
 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. 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
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.