StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14812651
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2013-02-11T13:09:11.713
FavoriteCount
0
LastActivityDate
2013-02-11T13:53:14.477
LastEditDate
2013-02-11T13:53:14.477
LastEditorUserId
85371
OwnerUserId
85371
ParentId
14811227
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<p>I can't see what's wrong: I've taken the effort to reconstruct your SSCCE.</p> <ul> <li><a href="http://liveworkspace.org/code/1pDtmn%241" rel="nofollow">http://liveworkspace.org/code/1pDtmn$1</a></li> </ul> <p>In the process, it seems I must have removed the problem. I suggest you do the same.</p> <h2>Oh, and this is how I'd write this:</h2> <ul> <li>no more phoenix</li> <li>no more constructors</li> <li>no more qi::locals</li> <li>no more needless copying</li> <li>using expectation points</li> </ul> <p>In short: no more fuss.</p> <pre><code>#include <boost/spirit/include/qi.hpp> #include <boost/fusion/adapted/struct.hpp> #include <cstdint> namespace qi = boost::spirit::qi; namespace chs = boost::spirit::ascii; //qi; typedef std::string::const_iterator StringIterator; struct Color { float r,g,b,a; }; BOOST_FUSION_ADAPT_STRUCT(Color, (float, r)(float, g)(float, b)(float, a)) template <typename ItType, typename Skipper> struct ColorGrammar : public qi::grammar<StringIterator, Color(), Skipper> { ColorGrammar() : ColorGrammar::base_type(rule_color, "color-grammar") { using namespace qi; rule_rgb = lit("rgb") >> '(' > float_ > ',' > float_ > ',' > float_ > attr(1.0f) > ')'; rule_rgba = lit("rgba") >> '(' > float_ > ',' > float_ > ',' > float_ > ',' > float_ > ')'; rule_color = rule_rgb | rule_rgba; } private: qi::uint_parser<uint8_t, 10, 1, 3> number; // unused qi::uint_parser<uint8_t, 16, 1, 1> hexdigit; // unused qi::rule<ItType, Color(), Skipper> rule_rgb, rule_rgba, rule_color; }; int main() { Color out; std::string str = " rgb ( 0.3 , .4 , 0.5 )"; StringIterator begin = str.cbegin(); StringIterator end = str.cend(); ColorGrammar<StringIterator, chs::space_type> color_; bool result = qi::phrase_parse(begin, end, color_, chs::space, out); std::cout << std::boolalpha << result << '\n'; std::cout << "remains: '" << std::string(begin, end) << "'\n"; } </code></pre> <p>Live on <a href="http://liveworkspace.org/code/35htD%243" rel="nofollow">http://liveworkspace.org/code/35htD$3</a></p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSkipper does not work in boost::spirit
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsehe
UserOwnerUserId
1. USsehe
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSkipper does not work in boost::spirit
  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
  VTUndeletion
3. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
CommentsPostId
1. COMuch better, I always forget about `attr` to specify default values. Though I believe that alpha should be the last value (for the case when the input is rgba).
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
2. CO@llonesmiz I completely agree, but I wanted to keep the grammar itself unaltered
  singulars
  PostPostId
  PO
  UserUserId
  USsehe
3. COWithout seeing the asker's constructors it's hard to say, but I would bet that in the original grammar _a->red, _b->green, _c->blue, _1->alpha.
  singulars
  PostPostId
  PO
  UserUserId
  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.