…perfectly fine of course! As the update keyword is BaseX-specific, your
code (in contrast to mine) will also run with other processors with support
for the File Module (such as Saxon).
Graydon Saunders schrieb am Mi., 26. Aug. 2020,
23:49:
> Hi Christian --
>
> Or I could just be a simple cr
Hi Chandra,
We’d appreciate to see a little XML document that allows us to test your
query.
Best
Christian
chandra sekhar n schrieb am Do., 27. Aug. 2020, 07:38:
> Dear Basex team,
> We are facing an xquery performance issue. Please find the query in below
> and please suggest any clue to op
Hi Srikumar,
The error message seems to have been raised from within the Spring
framework. Could you please provide us with some Java example code that we
can run without Spring?
Thanks in advance
Christian
Srikumar Choudhury schrieb am Do., 27. Aug. 2020,
06:57:
> Hi Christian,
> I am u
Dear Basex team,
We are facing an xquery performance issue. Please find the query in below
and please suggest any clue to optimize query
let $subbrk :=
(collection("867509_Voice_DECEMBER-19_Billed_1")/SUBCUSTBRK)
let $detailUsageTxn := $subbrk/DETAIL/TRANSACTION[@Usage = 'usage']
Hi Christian --
Or I could just be a simple creature and use
let $test as element(root) :=
{serialize(
words bold words
)}
return file:write('/home/graydon/test2.xml',
$test,
map { "method": "xml", "cdata-section-elements": "content"})
Which gives
(Your solution is consider
Hi Graydon,
I can’t say much about serialization in XSLT, but the serialization of
CDATA sections in XQuery is indeed focused on text nodes [1]:
“The cdata-section-elements parameter contains a list of expanded
QNames. If the expanded QName of the parent of a text node is a member
of the list,
Using 9.4.2 and 943-20200826.181852 I get the same result:
let $test as element(root) :=
words
return file:write('/home/graydon/test2.xml',
$test,
map { "method": "xml", "cdata-section-elements": "content"})
does not work, in the sense that no CDATA block is created.
let $test as el
Hi Rob,
An interesting one. The mixing of external nodes and node fragments (which
have different internal representations) caused some confusion.
The issue has been fixed, a new snapshot is ready to go [1].
All the best, hope you are fine,
Christian
[1] https://files.basex.org/releases/latest/
Hi Christian,
I encountered some inconsistency when using an fetched XML-node in combination
with xpath’s ancestor-axis.
I attached a small snippet. I expect an ancestor here.
It works alright if the XML-node is not fetched from a document or in case of
the parent-axis.
Best Regards,
Rob Sta
9 matches
Mail list logo