StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POFile Structure + Shared Features Between Controllers
primarykey
Id
5971141
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-11T22:02:43.600
FavoriteCount
0
LastActivityDate
2011-05-13T13:20:38.953
LastEditDate
2011-05-12T06:13:54.873
LastEditorUserId
636496
OwnerUserId
636496
ParentId
0
PostTypeId
1
Score
0
ViewCount
127
LastEditorDisplayName
text
Body
So im stuck with a file structure problem, i'm trying to find the best way not to repeat things. Im trying to get features shared with each extra section (Music, Movies, Shows etc). The Features being Likes, Recommendations, Tags and List. I'm looking for advice on how to structure it so there will be minimal repeating of code and easy secure access to the features for each section. The details are below. Also I am using Fuel PHP framework: <a href="http://fuelphp.com/" rel="nofollow">http://fuelphp.com/</a> There are listings: Music, Movies, Shows. (http://domain.com/music/view/1) Each listing supports Tags: (http://domain.com/music/tag/view/rock) So far that's easy, but features like 'likes' and 'recommendations' confuse me, as in I could have 'likes' in each listing's controller. Example (http://domain.com/music/like/1) or in its own controller (http://domain.com/like/music/1). Also each listing has 'recommendations' which list similar listings with reviews and 'Likes' for each recommendation. So 'likes' can be for listings and recommendations. Music (Model_Music)[one-to-one Model_List] -- Likes -- Tags (many-to-many) -- Recommendations (cross-reference by UNION) -- List (in this case all tracks and the song name) [one-to-many] Shows (Model_Shows)[one-to-one Model_List] -- Likes -- Tags (many-to-many) -- Recommendations (cross-reference by UNION) -- List (in this case all episode names and number)[one-to-many] As you can tell most of it will be the same code just with different URL structure and some changes on which table to use. I'm just not sure how to handle things best, just need a more experienced view on handling all these additional features to each listing music.php, shows.php, movies.php any any others that will be added.
Tags
<content-management-system><php><fuelphp>
Title
File Structure + Shared Features Between Controllers
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USDregondRahl
UserOwnerUserId
1. USDregondRahl
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.