StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1747380
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-11-17T08:33:50.430
FavoriteCount
0
LastActivityDate
2009-11-17T08:33:50.430
LastEditDate
LastEditorUserId
0
OwnerUserId
147192
ParentId
1742509
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Okay Let's get working (comments just allow so much). The problem stems from the invocation of the <code>find</code> method. The template elected is: <pre><code>template< typename CompatibleKey,typename CompatibleHash,typename CompatiblePred > iterator find(const CompatibleKey& k, const CompatibleHash& hash, const CompatiblePred& eq) const; </code></pre> With: <pre><code>KeyFromValue = composite_key<...> CompatibleKey = unique_property CompatibleHash = boost::hash<KeyFromValue> CompatiblePred = equal_to<KeyFromValue> </code></pre> Apparently, the invocation <code>hash(k)</code> inside the <code>find</code> method fails for the reason cited (could not deduce...), this methods itself invokes: <pre><code>template<BOOST_MULTI_INDEX_CK_ENUM_PARAMS(typename Value)> std::size_t operator()(const tuple<BOOST_MULTI_INDEX_CK_ENUM_PARAMS(Value)>& x)const </code></pre> (Don't be afraid by the macro, it's just some magic Boost.Preprocessor to enumerate the <code>Value</code> from 0 to 9) Now, from this we can see that the problem is that we try to build <code>tuple<Value0, Value1, ..., Value9></code> from <code>CompatibleKey</code> ie <code>unique_property</code> and it does not work. I think you should try: <pre><code>ProbLocByHugo::iterator pos = local_data_structure.get<hugo>().find(boost::make_tuple(tempy)); </code></pre> Here is the example of <code>composite_key</code> from [Boost][1]: <pre><code>file_system_by_name::iterator it=fs.find( boost::make_tuple(current_dir,dir)); boost::tie(it0,it1)=fs_by_size.equal_range( boost::make_tuple(current_dir)); </code></pre> As you can see, any invocation of key usage leads to <code>make_tuple</code>. You could avoid this by providing the right conversion operator for your <code>unique_property</code> class. <pre><code>operator boost::tuple< int, std::vector<int> const& >() const { return boost::make_tuple(my_int, cref(my_vec)); } </code></pre> Or perhaps a variation... I have to admit that I am a bit disappointed by this requirement, I would have expected that <code>find</code> would work seemlessly. [1] <a href="http://www.boost.org/doc/libs/1_40_0/libs/multi_index/example/composite_keys.cpp" rel="nofollow noreferrer">http://www.boost.org/doc/libs/1_40_0/libs/multi_index/example/composite_keys.cpp</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBoost Multi-Index with hashed_unique_index produces compiler error
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMatthieu M.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBoost Multi-Index with hashed_unique_index produces compiler error
 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
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COHi, thank you very much for your time and your solution! I tried your first approach but it didn't work right away. After thinking about your second suggestion I tried the following call: `ProbLocByHugo::iterator pos = local_data_structure.get<hugo>().find(boost::make_tuple(tempy.get_int(),tempy.get_vec()));` And that did the trick! Thank you again for your much appreciated help!! Have a great day!
 singulars
 PostPostId
 PO
 UserUserId
 USDane
2. COYou're welcome, I still don't get why this is not automatic anyway, as you have given the extraction method in template parameter...
 singulars
 PostPostId
 PO
 UserUserId
 USMatthieu M.

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.