StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5872226
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-05-03T15:55:08.490
FavoriteCount
0
LastActivityDate
2011-05-03T22:12:27.810
LastEditDate
2011-05-03T22:12:27.810
LastEditorUserId
534381
OwnerUserId
534381
ParentId
5871722
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
I think the visitor pattern can be a solution. UPDATE I finished my example: <pre><code>#include <iostream> #include <vector> #include <boost/shared_ptr.hpp> class Animal; class Wolf; class Fish; class Visitor { public: virtual void visit(const Animal& p_animal) const = 0; virtual void visit(const Wolf& p_animal) const = 0; virtual void visit(const Fish& p_animal) const = 0; }; template<class AMOUNT> class AmountVisitor : public Visitor { public: AmountVisitor(AMOUNT p_amount) : m_amount(p_amount) {} virtual void visit(const Animal& p_animal) const { std::cout << "I eat like a generic Animal." << std::endl; } virtual void visit(const Wolf& p_animal) const { std::cout << "I eat like a wolf!" << std::endl; } virtual void visit(const Fish& p_animal) const { std::cout << "I eat like a fish!" << std::endl; } AMOUNT m_amount; }; class Animal { public: virtual void Accept(const Visitor& p_visitor) const { p_visitor.visit(*this); } virtual ~Animal() { } }; class Wolf : public Animal { public: virtual void Accept(const Visitor& p_visitor) const { p_visitor.visit(*this); } }; class Fish : public Animal { public: virtual void Accept(const Visitor& p_visitor) const { p_visitor.visit(*this); } }; int main() { typedef boost::shared_ptr<Animal> TAnimal; std::vector<TAnimal> animals; animals.push_back(TAnimal(new Animal())); animals.push_back(TAnimal(new Wolf())); animals.push_back(TAnimal(new Fish())); AmountVisitor<int> amount(10); for (std::vector<TAnimal>::const_iterator it = animals.begin(); it != animals.end(); ++it) { (*it)->Accept(amount); } return 0; } </code></pre> this prints: <pre><code>I eat like a generic Animal. I eat like a wolf! I eat like a fish! </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to achieve "virtual template function" in C++
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USIndustrial-antidepressant
UserOwnerUserId
1. USIndustrial-antidepressant
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
CommentsPostId
1. COThank you. This is a nice solution as far as I understood it and I think, that this could also work for my problem designing Exporters instead of Animals. However, there is one thing I am wondering about: Would it be possible to realize something like a fallback-mechanism here, if e.g. an Animal gets an amount to eat that it can't eat the way it would usually do, but would then fallback to the generic way of "eating"?
 singulars
 PostPostId
 PO
 UserUserId
 USShadow
2. COIt is possible. For example you can use the chain-of-responsibility pattern in a visitor class. Just google "c++ chain-of-responsibility pattern".
 singulars
 PostPostId
 PO
 UserUserId
 USIndustrial-antidepressant

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.