StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1968145
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-12-28T05:51:10.447
FavoriteCount
0
LastActivityDate
2009-12-28T05:51:10.447
LastEditDate
LastEditorUserId
0
OwnerUserId
238762
ParentId
1967283
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Beware of diamond inheritance heirarchies. Also note that overloading virtual functions is a bad thing. So if you have something like this: <pre><code>class Handler : public EventHandler<int>, public EventHandler<string> { ... }; </code></pre> Which changeEvent() function will be called? Don't count on it! If you are careful the above code should be fine, but if you want to avoid inheritance altogether then I suggest using function references associated with some unique identifier. As an example: <pre><code>class Listener { public: virtual ~Listener ( ) { } }; template<typename Event> class Distributor : public Listener { public: void addListener (shared_ptr<Listener>, function<void (Event)>); void listen (Event e) { for_each(_listeners.begin(), _listeners.end(), bind(&ListenNode::listen, _1, e)); } private: struct ListenNode { weak_ptr<Listener> listener; function<void (Event)> callback; void listen (Event e) { shared_ptr<Listener> l = listener.lock(); if(l) callback(e); } }; list<ListenNode> _listeners; }; </code></pre> With this setup, all listeners derive from one base class virtually. Listeners can have multiple callbacks registered, and Distributors can be chained. Of course you don't have to use shared_ptr's but I like them because they save from the hassle of unregistering listeners. You can register the callbacks any way you like, associating them with a string, integer or whatever. I have omitted a lot of detail, event distribution is a complicated business. I think Andrei Alexandrescu wrote a detailed article on the topic, look it up. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMultiple inheritance on different template types
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USeclectocrat
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMultiple inheritance on different template types
 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. 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.