StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3633201
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-09-03T05:11:18.893
FavoriteCount
0
LastActivityDate
2010-09-03T05:11:18.893
LastEditDate
LastEditorUserId
0
OwnerUserId
38408
ParentId
3631422
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<p>Core behavior of OG is that every Content type defines it's own relationship to OG. They might be barred from a group relationship, a group node, or a group post. There is nothing in that base configuration to specify the relationship between a content type and each group type individually.</p> <p>However, there are a few tricks you could put in place to try to facilitate something.</p> <h3>Cheap Trick</h3> <p>For example, if you hide the navigation to create a node of a given content type, you've cut off the obvious approach.</p> <h3>OG User Roles</h3> <p>Probably the most conventional trick I can think of would be to carve up the different content types on a permissions level. I'm not entirely positive this will work, so it will bear some experimentation.</p> <ol> <li>Create a <em>Sports Writer</em> role, limit the ability to create and edit Basketball nodes to it.</li> <li>Use <a href="http://drupal.org/project/og_user_roles" rel="nofollow noreferrer">OG User Role</a> to automatically promote members of the Sports group types into the Sports Writer role. </li> </ol> <h3>Cutting Edge Shenanigans</h3> <p>You can also use the <a href="http://drupal.org/project/spaces" rel="nofollow noreferrer">Spaces</a> module to toggle content type availability by <a href="http://drupal.org/project/features" rel="nofollow noreferrer">Feature</a>. In fact, the implementation of spaces_menu_alter() might show you how you could programmatically build out the functionality you are looking for. Sounds like it would be useful.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOrganic Groups - types of nodes allowed to create
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGrayside
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POOrganic Groups - types of nodes allowed to create
  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
  VTAcceptedByOriginator
3. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. COthanks you kindly for the comments :) very usefull :)
  singulars
  PostPostId
  PO
  UserUserId
  USAnkh2054

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.