Why create Oracle SQL scripts to load the XML when you could use the Saxon SQL extensions with Oracle's JDBC driver?
 
Andy.


From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of Clapham, Paul
Sent: 30 April, 2008 17:12
To: Mailing list for the SAXON XSLT and XQuery processor
Subject: Re: [saxon] Creating a .Net Extension function

CLOBs have a limit of 2000 bytes? That doesn't sound right to me. I thought CLOBs could be very large, I thought it was regular varchar columns that were limited in size.
 
PC2


From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of Ryan Puddephatt
Sent: April 30, 2008 02:09
To: Mailing list for the SAXON XSLT and XQuery processor
Subject: ***SPAM*** Re: [saxon] Creating a .Net Extension function

Mike,

                I totally agree that XPath is the best way to manipulate nodes, but Iím using XSL to create an Oracle scripts that inserts XML into a database, unfortunately CLOBs have a limit of 2000 bytes so I need to split the XML into strings of 2000 bytes and then copy them back in, Iíve found that this would work for getting the node passed from Saxon, and then I can use OuterXml to get the value string value

 

        public static Array SplitXml(XPathContext c,object node) {

 

            if(node is System.Xml.XmlLinkedNode) {

 

Thanks

 

Ryan

-----------------------------------------------

Ryan Puddephatt

FIX Developer

Fidessa LatentZero

1 Alfred Place

London WC1E 7EB

t: +44 (0) 20 7323 6112

b: +44 (0) 79 8539 2458

f: +44 (0) 20 7462 4242

e: rpuddephatt@latentzero.com

w: http://www.latentzero.com