- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Wed, 04 Apr 2007 18:20:12 -0400
- To: public-xml-processing-model-wg@w3.org
Received on Wednesday, 4 April 2007 22:20:21 UTC
/ ht@inf.ed.ac.uk (Henry S. Thompson) was heard to say: | Nightmare! Yeah, fair enough. | Maybe we should delay discussing this until we've discussed errors, | because if we end up providing some kind of transaction support, some | of these problems will go away and/or be given useful background. Perhaps. | My inclination for v1 is to just say "no dependency mechanism", and | for now that you should build your db-update step to provide some form | of trivial output, e.g. | <my:wroteRecords n="3"/> | , and ignore it if you don't need it, but use it to sequence | subsequent steps if need be (e.g. in this case by wrapping the 'query' | step in a p:for-each select='my:wroteRecords'. . .) Yeah, that's a fair workaround. The for-each trick hadn't occurred to me. Be seeing you, norm -- Norman Walsh XML Standards Architect Sun Microsystems, Inc.
Received on Wednesday, 4 April 2007 22:20:21 UTC