StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6818046
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-25T14:56:21.373
FavoriteCount
0
LastActivityDate
2011-07-25T14:56:21.373
LastEditDate
LastEditorUserId
0
OwnerUserId
204819
ParentId
6812226
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You have two choices, both abstracted. First involves in creating Models and Controllers which Grid and other views would automatically recognise. With second, you would need to fetch data from MongoDB and insert into a static table. Mongo-aware Views This approach requires that you know how models operate. Particularly you'll need to understand MVCGrid, setController, setModel as well as mvc/Controller.php. You then would need to create your own controller. You would then need to have copy of AbstractView::setModel() which uses YOUR controller, which will properly know how to fetch data from MongoDB. Also you would probably need to extend Grid (or MVCGrid) to properly stream data. Once you have this done, you can do this: $form->setMongoModel('MyModel')->loadData(123); (if you are using GIT version, you can actually inject this method: <a href="https://github.com/atk4/atk4-testsuite/blob/master/page/core.php#L108" rel="nofollow">https://github.com/atk4/atk4-testsuite/blob/master/page/core.php#L108</a> Semi-automated approach In this approach you would need to load data from your MongoDB controller yourself and feed it into the grid or form. Both Grids and Forms can work with static data just fine. In this case you would need something like this: <pre><code>$c=$this->add('MongoController'); $data=$c->load($my_model,123); $grid->setStaticSource($data); </code></pre> <hr> Answers to your other questinos Code Igniter is nice framework, but it instantiates objects globally. It's unlikely you would need 2 instances of same library. Agile Toolkit permits that and Controllers are often used like that. As a result you are pretty much in charge of data management in CI while in ATK4 objects bind to each other. It's the core difference between approaches in those libraries. Library in CI: <pre><code>$this->load->library('MyLib'); </code></pre> in ATK4 would look like this: <pre><code>$this->api->add('MyLib'); </code></pre> It's common practice to place <pre><code>$this->owner->mylib=$this; </code></pre> inside your libraries, so it's easier for you to access them. You might be better off without knowing how PHP development happens, it's in most cases very reliant on HTML templates.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POagile toolkit 4 and implementing a different database (mongodb)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USromaninsh
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POagile toolkit 4 and implementing a different database (mongodb)
 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
 VTAcceptedByOriginator
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.