Hi Sean,
I would like to explicitly choose nodes to include in an index. For
> example, I would like to index nodes /a/b/c and /a/b/c/d/e or /a/b/c/d/f
> into a single index. I know that I can use wildcards for all descendents,
> but how can I do things like ands and ors to gain more control on the
> indexing? Any suggestions?
Seems that there is no way to do this at the moment. I think the easiest way
to manage with this is to create three different indexes and manipulate with
them properly at the query level.
> An alternative that looks like it will work is to index each node in a
> separate index and then use the | operator in the xquery/xpath expression,
> but that doesn't seem to work (at least how I tried it) in the path1 of an
> index expression to consolidate into one index.
Only simple (without predicates and function calls) path expressions are
allowed within the "create index" statement (
http://modis.ispras.ru/sedna/progguide/ProgGuidesu8.html#x14-480002.5.3).
Once again, you can create separate indexes for different path ways: for
example *index1* for */a/b/c* and *index2* for */a/b/e* and use "I" operator
in your query to connect results of the *index-scan()*.
Ivan Shcheklein,
Sedna Team
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
