when it comes to the problem description. Take your time.
>
> The mynsp:mytransform function would then look something as follows
>
> declare function spec:mytransform(args....) as element()*
> {
> <SomeTag>
> (
> ...code that then produces other sub elements. This is primarily
> achieved by calling other functions similar to this one. For example.
>
> spec:someTransform1(...),
> spec:someTransform2(...),
> etc.
> )
> <SomeTag>
> }
>
> Let me know if there is any other details you'd like or that I left out.
> Once again, I appreciate your efforts.
>
>
>
> On Monday, September 21, 2015 11:45 AM, Christian Grün
> <
christian.gruen@gmail.com> wrote:
>
>
> Once again, please provide us with more specific information, such as
> e.g. self-contained code snippets; otherwise we cannot help. There are
> simply too many ways to transform documents, query data, etc.
>
>
> On Mon, Sep 21, 2015 at 5:41 PM, <
buddyonweb-software@yahoo.com> wrote:
>> I am using BaseX to transform some an XML documents into another XML
>> layout.
>> When the incoming document gets large, run out of memory. I've bumped up
>> memory in the
>> JVM and that worked.
>>
>> However, what if there was a really large document? Is there a way to
>> redirect the output
>> so that instead of the results stored in memory they are sent to disk
>> somewhere (whether to a file
>> on the file system or even back into BaseX - destination doesn't quite
>> matter).
>>
>> Thanks.
>>
>
>