Support XML element argument type about uruk HOT 5 CLOSED

Version 0.2.6, now available, handles document-node and element variables given as a String, hiccup-style vector, or clojure.data.xml.Element.

from uruk.

I had intended to request that XML elements passed as arguments from Clojure would be arriving in the Query as element, not xs:string. I know that it is possible to parse the string to an XML element in the query, and it may actually be faster, yet I find that to be an extra step it would also look better if XML arguments could be declared as having the type element(). Can you investigate whether that'd be easy to implement and discuss if in doubt?

from uruk.

We're currently using Request.setNewVariable with ValueType set to element(), which from my research appears to be the extent that a variable passed in can be declared to be element(). As you say, it appears to still be necessary to xdmp:unquote or otherwise parse such a variable.

I will investigate further.

from uruk.

See http://developer.marklogic.com/pipermail/general/2016-July/019265.html

from uruk.

At this point I'm confident that Uruk is doing everything in its power to send XML elements through as elements. The variable type is set on the MarkLogic side, and in XQuery the node-kind is coming through as "element" without any casting:

(with-open [session (create-session db)]
  (execute-xquery session "xquery version \"1.0-ml\";
                           declare variable $my-variable external;
                           xdmp:node-kind($my-variable)"
                  {:variables {"my-variable" {:value "<foo/>"
                                              :type :element}}
                   :shape :single!}))
=> "element"

...therefore I am closing this for the moment. If other scenarios with XML element type issues arise, we can reopen.

from uruk.