Eric, Keep in mind that MarkLogic does not index element names independent of their namespace. So, *:foo cannot be resolved out of indexes. If you are evaluating an XPath expression across a database of many documents, this can be problematic. However, if you are within a document evaluating an XPath expression, chances are you won't really notice the difference. When possible, you should avoid *:foo for this reason.
Personally, I prefer the suggestion that Danny suggested of using a function. While we are on the subject, another thing MarkLogic indexes automatically is parent/child element pairs. So, rather than //foo, it is always better to say //foo/bar. Kelly Message: 7 Date: Mon, 23 Mar 2009 14:28:49 -0400 From: Eric Palmitesta <[email protected]> Subject: Re: [MarkLogic Dev General] quick namespace question To: General Mark Logic Developer Discussion <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=windows-1252; format=flowed Both of those options result in at least twice the number of lines as just using '*:' inline. If <a> is large, this becomes unmanageable. I guess I'll stick to '*:' for now. Thanks, EP _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
