Sorry, I realized my test was flawed and the map operator does seem to
interfere with concurrency. Does anyone know if there is any benefit of
using the map operator over a flwor other than simpler syntax?
On Sat, Oct 20, 2012 at 5:22 PM, Ryan Dew wrote:
> I know that flwor statements in certain
I know that flwor statements in certain situations can block concurrency.
I've done a couple simple tests that seem to indicate the map operator (!)
in ML6 doesn't break concurrency, but does anyone know for certain if there
is any difference with the map operator?
-Ryan Dew
_
The second variation looks like what you might get if the request-body is
parsed as XML when returned from xdmp:get-request-body(). As you've found out,
in that case calling xdmp:unquote is not a good idea, because it treats the
input as a string. So the result is the unquote of the fn:string(..
The behavior you describe is normal: you'll see similar behavior with built-in
databases like Schemas, Security, and Triggers.
The schemas-database setting tells the database where to look for schema
imports. For a custom schemas database, I think you'll only care about its own
schemas-database
