> .. I'm referring to the fact that -- as you explained -- you are reusing > DTM nodes to represent new data, and in streaming mode discarding some > nodes as you go, both of which break DTM APIs assumptions. You're counting > on understanding DTM usage well enough to write stylesheets which avoid > exposing these shortcuts.
The only thing that has caused trouble now and in the past is that the DTM document is being unnecessarily sorted. IMHO, this seems like a different issue and may relate to some performance problems. I am assuming that making the default "always sort" produces more consistent results. It is also strange that only the original/first XPath statement sorts the underlying document. i.e. If I apply-templates on "sql/row-set" then have a template named "row" then another called "col", it will work fine since there is only one row-set element so it sorts fine and then "row" template is not sorted. If the first template selects "sql/row-set/row" it will be sorted and you will only be left with a single row. (in Streaming mode) Regards John G
