On 07/03/2011 09:34, Florent Georges wrote:
> This is not a blocking issue for me, but I have to feed the
> output of a query to another query, so I thought to provide the
> second query as the destination of the first one (the same way it
> is possible to chain transforms to each other). But the class
> XQueryEvaluator does not implement Destination as XsltTransformer
> Is there any reason for that? Having this would allow more
> elegant user code, and well as not requiring the developer to
> buffer the output of the first query (or transform) explicitly
> into a tree in memory.
I have implemented this enhancement.
It doesn't use streaming at the moment - neither does the XSLT case.
Clearly it would be possible and desirable to make this kind of pipeline
use streaming rather than building intermediate trees, and I shall look
at that in due course.