<div><span class="gmail_quote">On 3/1/07, <b class="gmail_sendername">Chris Muller</b> <<a href="mailto:chris@funkyobjects.org">chris@funkyobjects.org</a>> wrote:</span></div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Brent!<br><br>I think you've cleverly solved your own question.. By indexing the reversed value, its no different than a keyword index where you can already query on the presence of multiple keywords, as in:
</blockquote>
<div>...</div>
<div><br> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">You don't even need a separate "reversed" index, just add two entries (the forward and reversed) for each object added to the collection.
</blockquote>
<div> </div>
<div>Actually, wouldn't this give you wrong results? That is, if in the normal collection you had "foobar" and "rabbit" and searched for '%bar', I think you would get back both "foobar" and "rabbit" (since it would match on raboof and rabbit, right?).
</div>
<div> </div>
<div>So, for safety, I would still suggest having 2 collections - or maybe tagging the collection with a notice if it is a reversed value or not.</div>
<div> </div>
<div>-ChrisC<br> </div>