On Aug 30, 2011, at 11:40 AM, Sanne Grinovero wrote:
Yes I understood that was your suggestions; but I think that using
@IndexEmbedded(depth=0, {IndexPath1, IndexPath2})
would get you exactly what you wanted?
Ahh gotcha. I misunderstood. Yes that works for me.
Just that I can still use for example depth=1 combined with some paths
to mean "all of depth 1, plus these extra paths we hand-picked".
Putting what you said(which I agree with) into example form:
@IndexEmbedded(depth=3, paths={"a.b.c.d.e"})
Would index everything up to depth 3. Additionally index a.b.c.d.e, which exceeds depth
of 3.
This flexibility seems handy to me, and makes the two features
compatible (not conflicting in any meaning), to the point that IMHO
they don't need new annotations.
Yeah this is much better. Thanks for clarifying.
ZK