No easy way right now, other than walk the expression tree. What I should
do is make a m_isStreamable flag on the StylesheetRoot, that I can set to
false if I encounter a WalkingInteratorSorted, a reverse-axis iterator, or
a xsl:sort element. Even so, you may only need this for a portion of the
stylesheet that you are using the extension with, so I'm not sure this a
great solution either.
Maybe we could make a special call into the DTM before we execute
WalkingInteratorSorted#setRoot?
-scott
John Gentilin
<jgentilin@sma To: [EMAIL PROTECTED]
rt911.com> cc: [EMAIL PROTECTED]
Subject: Re: SQL Extensions & Streaming
Mode
07/30/2001
04:15 PM
Scott,
What is the best way to determine that a WalkingInteratorSorted
has been called and what forces that to be called. Both the <xsl:for />
and an <xsl:copy-of /> both exercise this behavior when I would not
expect either to do so.
If there is a WIS present, should we just turn off streaming mode ??
How limited is the set of xsl to effectively use Streaming mode ??
Knowledge of when a WIS or other multi traversing iterators are used
may prove to be very beneficial when trying to achieve high performance.
Thanks
John G
[EMAIL PROTECTED] wrote:
> > Now the problem is, the method WalkingIteratorSorted#setRoot actually
>
> Well, the whole idea behind a streaming stylesheet is that a
> WalkingIteratorSorted should never be called. Unfortunately, sometimes a
> WalkingIteratorSorted is created when it shouldn't be.
>
> > Is there another place where I should be regulating access to the
> > ResultSet
>
> Probably the thing to do is, if streaming mode is on, check the
stylesheet
> to make sure no WalkingIteratorSorteds are present???
>
> -scott
--
--------------------------------------
John Gentilin
SMART911
18314 Carlwyn Drive
Castro Valley CA 94546
Contact Info
[EMAIL PROTECTED]
Phone 1-510-881-4821
--------------------------------------
(See attached file: jgentilin.vcf)
jgentilin.vcf
