StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15602300
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-03-24T18:26:56.447
FavoriteCount
0
LastActivityDate
2013-03-27T08:36:55.013
LastEditDate
2013-03-27T08:36:55.013
LastEditorUserId
1012616
OwnerUserId
1012616
ParentId
15596749
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
As far as I know <a href="https://github.com/joomla/jissues/" rel="nofollow">JIssues</a> is the only public example of using new MVC in Joomla CMS. While I find new MVC minimalism very convenient for Platform/ Framework applications, I'm reluctant to use it for new component for the reasons as you've written - it's missing some CMS-specific stuff. I think we (community) should develop these classes (available later in /libraries/cms/) taking into account new things in Joomla (MVC, Router, ApplicationWeb) as well as in PHP 5. <a href="https://github.com/joomla/jissues/tree/master/libraries/tracker/model" rel="nofollow">JModelTracker</a> might be a good thing to review Edit: There's an application built on Joomla Platform: <a href="http://cobaltcrm.org/" rel="nofollow">Cobalt CRM</a>. While it's not a CMS component, some design patterns are similar to how new MVC would be used in CMS: There's a base model <a href="https://github.com/cobaltcrm/cobalt/blob/master/libraries/crm/model/default.php" rel="nofollow">CobaltModelDefault</a> that other models extend (ie. <a href="https://github.com/cobaltcrm/cobalt/blob/master/libraries/crm/model/documents.php" rel="nofollow">CobaltModelDocuments</a>). For me it makes sense to prepare some classes for common use in CMS (that will probably be quite similar to legacy ones), but with RAD techniques in mind like <a href="https://akeeba.assembla.com/spaces/fof/wiki" rel="nofollow">Framework-on-Framework</a>, namespacing and so on.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBuilding a native Joomla 3.x component
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpiotr_cz
UserOwnerUserId
1. USpiotr_cz
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBuilding a native Joomla 3.x component
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks for your input. I had a close look at JModelTracker, most of the code is identical with the legacy classes (from what I've analyzed so far).
 singulars
 PostPostId
 PO
 UserUserId
 USValentin Despa
2. COOne more thing worth checking out might be the use of content tables in [Tags component](https://github.com/joomla/joomla-cms/blob/master/libraries/cms/tags/tags.php)
 singulars
 PostPostId
 PO
 UserUserId
 USpiotr_cz

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.