StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
917843
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-05-27T20:22:59.087
FavoriteCount
0
LastActivityDate
2009-05-27T20:22:59.087
LastEditDate
LastEditorUserId
0
OwnerUserId
107912
ParentId
907709
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
My understanding of Views 2 is that it is meant to work with information stored in a database. If you don't have access to the database against which the API was written, then consider writing the objects the API returns into a table. The easiest thing would probably be to create nodes from the objects. Then you could access them with Views 2. This is similar to the approach taken by the Acitivty Stream module (<a href="http://drupal.org/project/activitystream" rel="nofollow noreferrer">http://drupal.org/project/activitystream</a>). It creates nodes from the data returned by various APIs. Check out the module's code for examples of how to create the nodes: <a href="http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/activitystream/activitystream.module?view=markup" rel="nofollow noreferrer">http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/activitystream/activitystream.module?view=markup</a> On the other hand, if you have access to the source database, you might consider exposing the tables of that database to Views directly. This is the approach taken in the latest Views 2 integration code included with CiviCRM v2.2.3, which you can review here: <a href="http://svn.civicrm.org/civicrm/trunk/drupal/modules/views/" rel="nofollow noreferrer">http://svn.civicrm.org/civicrm/trunk/drupal/modules/views/</a> CiviCRM is a Drupal module that writes data to tables outside of the Drupal database -- not into nodes. The views integration code exposes most of those tables to Drupal. Hope this helps. -- Andrew B.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODrupal 6 - Views2 - How to build a view of non-nodes
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USandrew b
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODrupal 6 - Views2 - How to build a view of non-nodes
 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. 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.