StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16117372
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-04-20T06:20:27.647
FavoriteCount
0
LastActivityDate
2013-04-20T06:20:27.647
LastEditDate
LastEditorUserId
0
OwnerUserId
2251525
ParentId
16114886
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
I think it was just that your receive buffer was not null terminated. This code works: Server: <pre><code>#include <boost/interprocess/ipc/message_queue.hpp> #include <boost/serialization/string.hpp> #include <string> #include <sstream> #include <boost/property_tree/ptree.hpp> #include <boost/property_tree/json_parser.hpp> using boost::interprocess::message_queue; using boost::property_tree::ptree; using boost::property_tree::write_json; #define MAX_SIZE 1000 void send(ptree pt) { std::stringstream oss; write_json(oss,pt); message_queue mq(boost::interprocess::open_or_create,"coda",10,MAX_SIZE); mq.send(oss.str().c_str(), oss.str().size(),0); std::cout << oss.str() << std::endl; system("PAUSE"); } int main() { ptree pt; pt.put("prefix","standard"); pt.put("faceID",42); send(pt); } </code></pre> Client: <pre><code>#include <boost/interprocess/ipc/message_queue.hpp> #include <string> #include <strstream> #include <boost/property_tree/ptree.hpp> #include <boost/property_tree/json_parser.hpp> #include <boost/serialization/string.hpp> using boost::interprocess::message_queue; using boost::property_tree::ptree; using boost::property_tree::read_json; #define MAX_SIZE 1000 int main() { message_queue mq (boost::interprocess::open_or_create,"coda",10,MAX_SIZE); size_t recv_size; unsigned int priority; ptree pt; char buffer[MAX_SIZE]; mq.receive(buffer,MAX_SIZE,recv_size,priority); buffer[recv_size] = 0; std::istrstream is(buffer); read_json(is, pt); std::cout << "prefix: " << pt.get<std::string>("prefix") << " -- faceID: " << pt.get<std::string>("faceID") << std::endl; system("PAUSE"); } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC++ boost json ptree parser fail to parse string
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPeter R
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POC++ boost json ptree parser fail to parse string
 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
CommentsPostId
1. COyeah, seems to works, thanks, i was doing a lot of useless stuff because i didn't understand how it worked properly and made a lot of confusion
 singulars
 PostPostId
 PO
 UserUserId
 USkurojishi

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.