Hello *,<div><br></div><div>reading this page states only that iterator validity is preserved for hashed indices. I have a multi-index container with ordered_non_unique entries.</div><div><br></div><div>Is it safe to find a matching range and modify the keys there?</div>

<div><br></div><div>Here an example:</div><div><br></div><div><div>    entry_data&amp; entries = indexed; //get the view to the MI-Container</div><div><br></div><div>    for(iterator_range&lt;entry_data::iterator&gt; r </div>

<div>          = entries.equal_range(boost::make_tuple(false))</div><div>        ; !r.empty()</div><div>        ; r.advance_begin(1)</div><div>       )</div><div>    {</div><div>      index_data d = r.front();</div><div>
      d.masked = true;</div>
<div>      entries.replace(r.begin(), d);</div><div>    }</div></div><div><br></div><div>Here updated d.masked field is a first member of the composite key. What happens if I do the update as shown upon?</div><div><br></div>

<div><br></div><div><br></div><div>Would it be more efficient to iterate backwards and do the update, since than all the elements will not be rearranged?</div><div><br></div><div>Is there also any way to use modify_key with composite index or are composite index key extractors always read-only?</div>

<div><br></div><div><br></div><div><br></div><div>With Kind Regards,</div><div>Ovanes</div><div><br></div><div><br></div>