
9 Jul
2011
9 Jul
'11
4:58 p.m.
I've found the problem. I broke the constancy rule on the container, like a true noob. Objects were being added to the container with a temporary ExchID, and then subsequently the ExchID's for each object were updated, making the ExchID index corrupt. Whenever I listed the container objects, they looked fine, and the index looked OK. The corruption gave me a 50-50 hit rate on finding objects using that index, which had me confused to say the least. And all it took was a couple of days to discover. -- View this message in context: http://boost.2283326.n4.nabble.com/Multi-Index-Container-find-not-working-wi... Sent from the Boost - Users mailing list archive at Nabble.com.