Watson, John wrote:
> I find SQL/XML hits the sweet spot for me. Currently I need to interrogate a
> single relational schema in order to generate XML, which can later be styled
> to whatever output format is required using XSLT. SQL/XML is ideal - it
> doesn't require much more stuff to learn - just a bunch of XML generating
> primitives layered on top of nested queries, which is reasonably
> straightforward, although I find I easily get lost in the bracketing!
I'm curious as to why you use XSLT as opposed to just generating the
result you want straight from the database with SQL/XML. Is it just too
hard from a programming standpoint? Do you perform multiple transforms
on the same result? etc.
-- Ron
