Main Page » Mailing List » January 2020

Help with a Query/Performance

Monday, 20 January 2020 · 5 messages · last reply 22 Jan 2020
TU
Tom Rauchenwald (UNIFITS)20 Jan 2020 10:01 #
Hi list, I'm struggling with a query. We have XML documents with a structure similar to this:
<Container>
  <ContainerMetaData1>FOO</ContainerMetaData1>
  <ContainerMetaData2>FOO</ContainerMetaData2>
  <MessageA>
    <MessageAMetaData>
      <MessageMetaData1>FOO</MessageMetaData1>
      <MessageMetaData2>FOO</MessageMetaData2>
    </MessageAMetaData>
    <MessageADetail>
      <DetailData1>FOO</DetailData1>
      <DetailData2>FOO</DetailData2>
    </MessageADetail>
    <MessageADetail>
      <DetailData1>FOO</DetailData1>
      <DetailData2>FOO</DetailData2>
    </MessageADetail>
  </MessageA>
  <MessageB>
    <MessageBMetaData>
      <MessageMetaData1>FOO</MessageMetaData1>
      <MessageMetaData2>FOO</MessageMetaData2>
    </MessageBMetaData>
    <MessageBDetail>
      <DetailData1>FOO</DetailData1>
      <DetailData2>FOO</DetailData2>
    </MessageBDetail>
  </MessageB>
  <MessageC>
    <MessageCMetaData>
      <MessageMetaData1>FOO</MessageMetaData1>
      <MessageMetaData2>FOO</MessageMetaData2>
    </MessageCMetaData>
    <MessageCDetail>
      <DetailData1>FOO</DetailData1>
      <DetailData2>FOO</DetailData2>
    </MessageCDetail>
  </MessageC>
</Container>
Messages are bundled in a container (up to n times for each message), and each message has details (also up to n times). Container, Message contain data that is the same for all details (it's basically a grouping). I'd like to retrieve a Detail with all corresponding data associated with it, so basically a MessageADetail, MessageA (without all the other MessageADetails), Container (without all the other Messages). I know the position of the message (i.e., I know that I want the second MessageA for example), and I know the position of the Detail (i.e., I know that I want the 3rd Detail). The use case is to show the detail in context in a UI. The query to do this I came up with is (here I want to get the 2nd detail from the third MessageA):
  let $fh := (copy $x := /*:Container
   modify ( delete node $x/*:MessageA[position() != 3]
          , delete node $x/*:MessageA[3]/*:MessageADetail[position() != 2]
          , delete node $x/*:MessageB
          , delete node $x/*:MessageC
          )
  return $x)
  return $fh
This works well for small documents. For large documents it can take a couple of seconds to evaluate the query (our real-life documents do have more data/elements in Details and Message). I'm wondering if there's a better/more efficient way to do this. I tried formulating a query that doesn't do deletes, but I couldn't come up with a solution that performs better and is correct. Any pointers would be very much appreciated. Here's a function to generate sufficiently large test data:
declare function local:sample($numberOfMessages, $numberOfDetails) {
<Container>
  <ContainerMetaData1>FOO</ContainerMetaData1>
  <ContainerMetaData2>FOO</ContainerMetaData2>
  {for $i in 1 to $numberOfMessages
    return
  <MessageA>
    <MessageAMetaData>
      <MessageMetaData1>FOO {$i}</MessageMetaData1>
      <MessageMetaData2>FOO {$i}</MessageMetaData2>
    </MessageAMetaData>
    {for $j in 1 to $numberOfDetails
     return
     <MessageADetail>
       <DetailData1>FOO {$j}</DetailData1>
       <DetailData2>FOO {$j}</DetailData2>
     </MessageADetail>
    }
  </MessageA>
  }
  <MessageB>
    <MessageBMetaData>
      <MessageMetaData1>FOO</MessageMetaData1>
      <MessageMetaData2>FOO</MessageMetaData2>
    </MessageBMetaData>
    <MessageBDetail>
      <DetailData1>FOO</DetailData1>
      <DetailData2>FOO</DetailData2>
    </MessageBDetail>
  </MessageB>
  <MessageC>
    <MessageCMetaData>
      <MessageMetaData1>FOO</MessageMetaData1>
      <MessageMetaData2>FOO</MessageMetaData2>
    </MessageCMetaData>
    <MessageCDetail>
      <DetailData1>FOO</DetailData1>
      <DetailData2>FOO</DetailData2>
    </MessageCDetail>
  </MessageC>
</Container>
};

db:create('tr-test', local:sample(20, 100000), 'test.xml')
Thanks, Tom Rauchenwald
ZD
Zimmel, Daniel20 Jan 2020 10:57 #
Hi Tom, I think that trying to copy/modify a huge tree is definitely the bottleneck here. Why don’t you copy only your third Message element and then reconstruct the wrapping Container with ContainerMetaData? Since the wanted result is a transformation, perhaps a typeswitch expression might be an alternative, if there is something that stops you from reconstructing. Daniel
Quoted text · Tom Rauchenwald (UNIFITS) · 107 lines
Von: Tom Rauchenwald (UNIFITS) <tom.rauchenwald at unifits.com> Gesendet: Montag, 20. Januar 2020 10:01 An: basex-talk at mailman.uni-konstanz.de Betreff: [basex-talk] Help with a Query/Performance Hi list, I'm struggling with a query. We have XML documents with a structure similar to this: <Container> <ContainerMetaData1>FOO</ContainerMetaData1> <ContainerMetaData2>FOO</ContainerMetaData2> <MessageA> <MessageAMetaData> <MessageMetaData1>FOO</MessageMetaData1> <MessageMetaData2>FOO</MessageMetaData2> </MessageAMetaData> <MessageADetail> <DetailData1>FOO</DetailData1> <DetailData2>FOO</DetailData2> </MessageADetail> <MessageADetail> <DetailData1>FOO</DetailData1> <DetailData2>FOO</DetailData2> </MessageADetail> </MessageA> <MessageB> <MessageBMetaData> <MessageMetaData1>FOO</MessageMetaData1> <MessageMetaData2>FOO</MessageMetaData2> </MessageBMetaData> <MessageBDetail> <DetailData1>FOO</DetailData1> <DetailData2>FOO</DetailData2> </MessageBDetail> </MessageB> <MessageC> <MessageCMetaData> <MessageMetaData1>FOO</MessageMetaData1> <MessageMetaData2>FOO</MessageMetaData2> </MessageCMetaData> <MessageCDetail> <DetailData1>FOO</DetailData1> <DetailData2>FOO</DetailData2> </MessageCDetail> </MessageC> </Container> Messages are bundled in a container (up to n times for each message), and each message has details (also up to n times). Container, Message contain data that is the same for all details (it's basically a grouping). I'd like to retrieve a Detail with all corresponding data associated with it, so basically a MessageADetail, MessageA (without all the other MessageADetails), Container (without all the other Messages). I know the position of the message (i.e., I know that I want the second MessageA for example), and I know the position of the Detail (i.e., I know that I want the 3rd Detail). The use case is to show the detail in context in a UI. The query to do this I came up with is (here I want to get the 2nd detail from the third MessageA): let $fh := (copy $x := /*:Container modify ( delete node $x/*:MessageA[position() != 3] , delete node $x/*:MessageA[3]/*:MessageADetail[position() != 2] , delete node $x/*:MessageB , delete node $x/*:MessageC ) return $x) return $fh This works well for small documents. For large documents it can take a couple of seconds to evaluate the query (our real-life documents do have more data/elements in Details and Message). I'm wondering if there's a better/more efficient way to do this. I tried formulating a query that doesn't do deletes, but I couldn't come up with a solution that performs better and is correct. Any pointers would be very much appreciated. Here's a function to generate sufficiently large test data: declare function local:sample($numberOfMessages, $numberOfDetails) { <Container> <ContainerMetaData1>FOO</ContainerMetaData1> <ContainerMetaData2>FOO</ContainerMetaData2> {for $i in 1 to $numberOfMessages return <MessageA> <MessageAMetaData> <MessageMetaData1>FOO {$i}</MessageMetaData1> <MessageMetaData2>FOO {$i}</MessageMetaData2> </MessageAMetaData> {for $j in 1 to $numberOfDetails return <MessageADetail> <DetailData1>FOO {$j}</DetailData1> <DetailData2>FOO {$j}</DetailData2> </MessageADetail> } </MessageA> } <MessageB> <MessageBMetaData> <MessageMetaData1>FOO</MessageMetaData1> <MessageMetaData2>FOO</MessageMetaData2> </MessageBMetaData> <MessageBDetail> <DetailData1>FOO</DetailData1> <DetailData2>FOO</DetailData2> </MessageBDetail> </MessageB> <MessageC> <MessageCMetaData> <MessageMetaData1>FOO</MessageMetaData1> <MessageMetaData2>FOO</MessageMetaData2> </MessageCMetaData> <MessageCDetail> <DetailData1>FOO</DetailData1> <DetailData2>FOO</DetailData2> </MessageCDetail> </MessageC> </Container> }; db:create('tr-test', local:sample(20, 100000), 'test.xml') Thanks, Tom Rauchenwald
CG
Christian Grünin reply to Tom Rauchenwald (UNIFITS), 20 Jan 2020, 10:0120 Jan 2020 18:54 #
Dear Tom, If you have large elements, it will usually be faster to create new elements. Here’s one way to do it:
  let $offset1 := 3
  let $offset2 := 2
  let $container := db:open('tr-test')/Container
  return element Container {
    (: add meta data elements :)
    $container/*[starts-with(name(), 'ContainerMetaData')],
    (: alternative: add everything except Message elements
    $container/(* except (MessageA, MessageB, MessageC)), :)
    $container/MessageA[$offset1] update {
      delete node MessageADetail[position() != $offset2]
    }
  }
There are probably ways to get this even faster; I may have a look at this tomorrow. All the best from Konstanz, Christian
Quoted text · Tom Rauchenwald (UNIFITS) · 120 lines
On Mon, Jan 20, 2020 at 10:01 AM Tom Rauchenwald (UNIFITS) <tom.rauchenwald at unifits.com> wrote: > > Hi list, > > I'm struggling with a query. > > We have XML documents with a structure similar to this: > > <Container> > <ContainerMetaData1>FOO</ContainerMetaData1> > <ContainerMetaData2>FOO</ContainerMetaData2> > <MessageA> > <MessageAMetaData> > <MessageMetaData1>FOO</MessageMetaData1> > <MessageMetaData2>FOO</MessageMetaData2> > </MessageAMetaData> > <MessageADetail> > <DetailData1>FOO</DetailData1> > <DetailData2>FOO</DetailData2> > </MessageADetail> > <MessageADetail> > <DetailData1>FOO</DetailData1> > <DetailData2>FOO</DetailData2> > </MessageADetail> > </MessageA> > <MessageB> > <MessageBMetaData> > <MessageMetaData1>FOO</MessageMetaData1> > <MessageMetaData2>FOO</MessageMetaData2> > </MessageBMetaData> > <MessageBDetail> > <DetailData1>FOO</DetailData1> > <DetailData2>FOO</DetailData2> > </MessageBDetail> > </MessageB> > <MessageC> > <MessageCMetaData> > <MessageMetaData1>FOO</MessageMetaData1> > <MessageMetaData2>FOO</MessageMetaData2> > </MessageCMetaData> > <MessageCDetail> > <DetailData1>FOO</DetailData1> > <DetailData2>FOO</DetailData2> > </MessageCDetail> > </MessageC> > </Container> > > Messages are bundled in a container (up to n times for each message), and each message has details (also up to n times). Container, Message contain data that is the same for all details (it's basically a grouping). > I'd like to retrieve a Detail with all corresponding data associated with it, so basically a MessageADetail, MessageA (without all the other MessageADetails), Container (without all the other Messages). > I know the position of the message (i.e., I know that I want the second MessageA for example), and I know the position of the Detail (i.e., I know that I want the 3rd Detail). > The use case is to show the detail in context in a UI. > > The query to do this I came up with is (here I want to get the 2nd detail from the third MessageA): > > let $fh := (copy $x := /*:Container > modify ( delete node $x/*:MessageA[position() != 3] > , delete node $x/*:MessageA[3]/*:MessageADetail[position() != 2] > , delete node $x/*:MessageB > , delete node $x/*:MessageC > ) > return $x) > return $fh > > This works well for small documents. For large documents it can take a couple of seconds to evaluate the query (our real-life documents do have more data/elements in Details and Message). > I'm wondering if there's a better/more efficient way to do this. I tried formulating a query that doesn't do deletes, but I couldn't come up with a solution that performs better and is correct. > > Any pointers would be very much appreciated. > > Here's a function to generate sufficiently large test data: > > declare function local:sample($numberOfMessages, $numberOfDetails) { > <Container> > <ContainerMetaData1>FOO</ContainerMetaData1> > <ContainerMetaData2>FOO</ContainerMetaData2> > {for $i in 1 to $numberOfMessages > return > <MessageA> > <MessageAMetaData> > <MessageMetaData1>FOO {$i}</MessageMetaData1> > <MessageMetaData2>FOO {$i}</MessageMetaData2> > </MessageAMetaData> > {for $j in 1 to $numberOfDetails > return > <MessageADetail> > <DetailData1>FOO {$j}</DetailData1> > <DetailData2>FOO {$j}</DetailData2> > </MessageADetail> > } > </MessageA> > } > <MessageB> > <MessageBMetaData> > <MessageMetaData1>FOO</MessageMetaData1> > <MessageMetaData2>FOO</MessageMetaData2> > </MessageBMetaData> > <MessageBDetail> > <DetailData1>FOO</DetailData1> > <DetailData2>FOO</DetailData2> > </MessageBDetail> > </MessageB> > <MessageC> > <MessageCMetaData> > <MessageMetaData1>FOO</MessageMetaData1> > <MessageMetaData2>FOO</MessageMetaData2> > </MessageCMetaData> > <MessageCDetail> > <DetailData1>FOO</DetailData1> > <DetailData2>FOO</DetailData2> > </MessageCDetail> > </MessageC> > </Container> > }; > > db:create('tr-test', local:sample(20, 100000), 'test.xml') > > Thanks, > Tom Rauchenwald > >
CG
Christian Grün20 Jan 2020 19:06 #
I missed to do the obvious next step. The following query is evaluated in a few milliseconds:
  declare variable $OFFSET1 := 3;
  declare variable $OFFSET2 := 2;

  let $container := db:open('tr-test')/Container
  let $message := $container/*:MessageA[$OFFSET1]
  let $detail := $message/MessageADetail[$OFFSET2]
  return element { name($container) } {
    $container/*[contains(name(), 'MetaData')],
    element { name($message) } {
      $message/MessageAMetaData,
      element { name($detail) } {
        $detail/*
      }
    }
  }
Quoted text · Christian Grün · 149 lines
On Mon, Jan 20, 2020 at 6:54 PM Christian Grün <christian.gruen at gmail.com> wrote: > > Dear Tom, > > If you have large elements, it will usually be faster to create new > elements. Here’s one way to do it: > > let $offset1 := 3 > let $offset2 := 2 > let $container := db:open('tr-test')/Container > return element Container { > (: add meta data elements :) > $container/*[starts-with(name(), 'ContainerMetaData')], > (: alternative: add everything except Message elements > $container/(* except (MessageA, MessageB, MessageC)), :) > $container/MessageA[$offset1] update { > delete node MessageADetail[position() != $offset2] > } > } > > There are probably ways to get this even faster; I may have a look at > this tomorrow. > > All the best from Konstanz, > Christian > > > > On Mon, Jan 20, 2020 at 10:01 AM Tom Rauchenwald (UNIFITS) > <tom.rauchenwald at unifits.com> wrote: > > > > Hi list, > > > > I'm struggling with a query. > > > > We have XML documents with a structure similar to this: > > > > <Container> > > <ContainerMetaData1>FOO</ContainerMetaData1> > > <ContainerMetaData2>FOO</ContainerMetaData2> > > <MessageA> > > <MessageAMetaData> > > <MessageMetaData1>FOO</MessageMetaData1> > > <MessageMetaData2>FOO</MessageMetaData2> > > </MessageAMetaData> > > <MessageADetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageADetail> > > <MessageADetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageADetail> > > </MessageA> > > <MessageB> > > <MessageBMetaData> > > <MessageMetaData1>FOO</MessageMetaData1> > > <MessageMetaData2>FOO</MessageMetaData2> > > </MessageBMetaData> > > <MessageBDetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageBDetail> > > </MessageB> > > <MessageC> > > <MessageCMetaData> > > <MessageMetaData1>FOO</MessageMetaData1> > > <MessageMetaData2>FOO</MessageMetaData2> > > </MessageCMetaData> > > <MessageCDetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageCDetail> > > </MessageC> > > </Container> > > > > Messages are bundled in a container (up to n times for each message), and each message has details (also up to n times). Container, Message contain data that is the same for all details (it's basically a grouping). > > I'd like to retrieve a Detail with all corresponding data associated with it, so basically a MessageADetail, MessageA (without all the other MessageADetails), Container (without all the other Messages). > > I know the position of the message (i.e., I know that I want the second MessageA for example), and I know the position of the Detail (i.e., I know that I want the 3rd Detail). > > The use case is to show the detail in context in a UI. > > > > The query to do this I came up with is (here I want to get the 2nd detail from the third MessageA): > > > > let $fh := (copy $x := /*:Container > > modify ( delete node $x/*:MessageA[position() != 3] > > , delete node $x/*:MessageA[3]/*:MessageADetail[position() != 2] > > , delete node $x/*:MessageB > > , delete node $x/*:MessageC > > ) > > return $x) > > return $fh > > > > This works well for small documents. For large documents it can take a couple of seconds to evaluate the query (our real-life documents do have more data/elements in Details and Message). > > I'm wondering if there's a better/more efficient way to do this. I tried formulating a query that doesn't do deletes, but I couldn't come up with a solution that performs better and is correct. > > > > Any pointers would be very much appreciated. > > > > Here's a function to generate sufficiently large test data: > > > > declare function local:sample($numberOfMessages, $numberOfDetails) { > > <Container> > > <ContainerMetaData1>FOO</ContainerMetaData1> > > <ContainerMetaData2>FOO</ContainerMetaData2> > > {for $i in 1 to $numberOfMessages > > return > > <MessageA> > > <MessageAMetaData> > > <MessageMetaData1>FOO {$i}</MessageMetaData1> > > <MessageMetaData2>FOO {$i}</MessageMetaData2> > > </MessageAMetaData> > > {for $j in 1 to $numberOfDetails > > return > > <MessageADetail> > > <DetailData1>FOO {$j}</DetailData1> > > <DetailData2>FOO {$j}</DetailData2> > > </MessageADetail> > > } > > </MessageA> > > } > > <MessageB> > > <MessageBMetaData> > > <MessageMetaData1>FOO</MessageMetaData1> > > <MessageMetaData2>FOO</MessageMetaData2> > > </MessageBMetaData> > > <MessageBDetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageBDetail> > > </MessageB> > > <MessageC> > > <MessageCMetaData> > > <MessageMetaData1>FOO</MessageMetaData1> > > <MessageMetaData2>FOO</MessageMetaData2> > > </MessageCMetaData> > > <MessageCDetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageCDetail> > > </MessageC> > > </Container> > > }; > > > > db:create('tr-test', local:sample(20, 100000), 'test.xml') > > > > Thanks, > > Tom Rauchenwald > > > >
TU
Tom Rauchenwald (UNIFITS)22 Jan 2020 07:29 #
Hi Christian, thanks for the help! I have a working version of this now that performs well. Initially I didn't want to reconstruct parts of the message, because we have a couple of different versions of these containers and usually there are multiple namespaces and prefixes involved that should be preserved. But it turns out this was easier than I thought. Thanks & greetings from Salzburg, Tom
Quoted text · Christian Grün · 170 lines
Von: Christian Grün <christian.gruen at gmail.com> Gesendet: Montag, 20. Jänner 2020 19:06 An: Tom Rauchenwald (UNIFITS) <tom.rauchenwald at unifits.com> Cc: basex-talk at mailman.uni-konstanz.de <basex-talk at mailman.uni-konstanz.de> Betreff: Re: [basex-talk] Help with a Query/Performance I missed to do the obvious next step. The following query is evaluated in a few milliseconds: declare variable $OFFSET1 := 3; declare variable $OFFSET2 := 2; let $container := db:open('tr-test')/Container let $message := $container/*:MessageA[$OFFSET1] let $detail := $message/MessageADetail[$OFFSET2] return element { name($container) } { $container/*[contains(name(), 'MetaData')], element { name($message) } { $message/MessageAMetaData, element { name($detail) } { $detail/* } } } On Mon, Jan 20, 2020 at 6:54 PM Christian Grün <christian.gruen at gmail.com> wrote: > > Dear Tom, > > If you have large elements, it will usually be faster to create new > elements. Here’s one way to do it: > > let $offset1 := 3 > let $offset2 := 2 > let $container := db:open('tr-test')/Container > return element Container { > (: add meta data elements :) > $container/*[starts-with(name(), 'ContainerMetaData')], > (: alternative: add everything except Message elements > $container/(* except (MessageA, MessageB, MessageC)), :) > $container/MessageA[$offset1] update { > delete node MessageADetail[position() != $offset2] > } > } > > There are probably ways to get this even faster; I may have a look at > this tomorrow. > > All the best from Konstanz, > Christian > > > > On Mon, Jan 20, 2020 at 10:01 AM Tom Rauchenwald (UNIFITS) > <tom.rauchenwald at unifits.com> wrote: > > > > Hi list, > > > > I'm struggling with a query. > > > > We have XML documents with a structure similar to this: > > > > <Container> > > <ContainerMetaData1>FOO</ContainerMetaData1> > > <ContainerMetaData2>FOO</ContainerMetaData2> > > <MessageA> > > <MessageAMetaData> > > <MessageMetaData1>FOO</MessageMetaData1> > > <MessageMetaData2>FOO</MessageMetaData2> > > </MessageAMetaData> > > <MessageADetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageADetail> > > <MessageADetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageADetail> > > </MessageA> > > <MessageB> > > <MessageBMetaData> > > <MessageMetaData1>FOO</MessageMetaData1> > > <MessageMetaData2>FOO</MessageMetaData2> > > </MessageBMetaData> > > <MessageBDetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageBDetail> > > </MessageB> > > <MessageC> > > <MessageCMetaData> > > <MessageMetaData1>FOO</MessageMetaData1> > > <MessageMetaData2>FOO</MessageMetaData2> > > </MessageCMetaData> > > <MessageCDetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageCDetail> > > </MessageC> > > </Container> > > > > Messages are bundled in a container (up to n times for each message), and each message has details (also up to n times). Container, Message contain data that is the same for all details (it's basically a grouping). > > I'd like to retrieve a Detail with all corresponding data associated with it, so basically a MessageADetail, MessageA (without all the other MessageADetails), Container (without all the other Messages). > > I know the position of the message (i.e., I know that I want the second MessageA for example), and I know the position of the Detail (i.e., I know that I want the 3rd Detail). > > The use case is to show the detail in context in a UI. > > > > The query to do this I came up with is (here I want to get the 2nd detail from the third MessageA): > > > > let $fh := (copy $x := /*:Container > > modify ( delete node $x/*:MessageA[position() != 3] > > , delete node $x/*:MessageA[3]/*:MessageADetail[position() != 2] > > , delete node $x/*:MessageB > > , delete node $x/*:MessageC > > ) > > return $x) > > return $fh > > > > This works well for small documents. For large documents it can take a couple of seconds to evaluate the query (our real-life documents do have more data/elements in Details and Message). > > I'm wondering if there's a better/more efficient way to do this. I tried formulating a query that doesn't do deletes, but I couldn't come up with a solution that performs better and is correct. > > > > Any pointers would be very much appreciated. > > > > Here's a function to generate sufficiently large test data: > > > > declare function local:sample($numberOfMessages, $numberOfDetails) { > > <Container> > > <ContainerMetaData1>FOO</ContainerMetaData1> > > <ContainerMetaData2>FOO</ContainerMetaData2> > > {for $i in 1 to $numberOfMessages > > return > > <MessageA> > > <MessageAMetaData> > > <MessageMetaData1>FOO {$i}</MessageMetaData1> > > <MessageMetaData2>FOO {$i}</MessageMetaData2> > > </MessageAMetaData> > > {for $j in 1 to $numberOfDetails > > return > > <MessageADetail> > > <DetailData1>FOO {$j}</DetailData1> > > <DetailData2>FOO {$j}</DetailData2> > > </MessageADetail> > > } > > </MessageA> > > } > > <MessageB> > > <MessageBMetaData> > > <MessageMetaData1>FOO</MessageMetaData1> > > <MessageMetaData2>FOO</MessageMetaData2> > > </MessageBMetaData> > > <MessageBDetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageBDetail> > > </MessageB> > > <MessageC> > > <MessageCMetaData> > > <MessageMetaData1>FOO</MessageMetaData1> > > <MessageMetaData2>FOO</MessageMetaData2> > > </MessageCMetaData> > > <MessageCDetail> > > <DetailData1>FOO</DetailData1> > > <DetailData2>FOO</DetailData2> > > </MessageCDetail> > > </MessageC> > > </Container> > > }; > > > > db:create('tr-test', local:sample(20, 100000), 'test.xml') > > > > Thanks, > > Tom Rauchenwald > > > >

Written for BaseX 9.3. BaseX may have changed since: please check the current documentation.

« An invalid XML character (Unicode: 0x1a) was found in the element content of the documentHow to escape/encode a search term using BaseX REST XQ »
⚡Generated with XQuery