Stef wrote:
Hello Barry,
I do not disagree with you, but (sadly ?) the database
that is used here is Sybase, and not even an 'upto date'
version either (12.0). I am not at liberty to change the underlying
database technology sadly, but, them's the breaks.
Sybase has a bulk load utility called bcp (at least that is what it used
to be called). If you can get your data into a set of INSERT statements
you can create a file that bcp can use. If your update operation is
complex - referential constraints, lookups, unusual condition handling -
you may be better served with a hybrid approach. You could load your
data into a set of staging tables then process it with a stored
procedure or program to get it into its final form. This last step has
nothing to do with XSL but the overall approach is not that atypical:
process your XML using XSL then let another more task-specific tool
process the output. I have done exactly this with Oracle as the target
but a Sybase-based approach would only differ in the detailed syntax.
Barry
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--