Persist recordset as XML, or cook XML w/ XMLDSO 
Author Message
 Persist recordset as XML, or cook XML w/ XMLDSO

I am pulling data from a database, converting it to XML, and rendering it as
HTML using XSL.  I seem to have (at least) 2 choices when it comes to
converting the data to XML
(1) call Recordset::Save with adPersistXML or (2) use an ASP page and the
XMLDSO to generate XML.

The first technique requires I create a disk file for the Save, and I deal
with the XML the Recordset writes.  With the second technique I can invent
my own XML document type and the XML never needs touch disk.

My main reservation about using Recordset::Save concerns the XML document
format.  Is the Recordset generated XML in documented and fixed format, or
is it an undocumented/unsupported format likely to change?

Thanks,
Ed Schiebel



Mon, 17 Sep 2001 03:00:00 GMT
 Persist recordset as XML, or cook XML w/ XMLDSO

Using Recordset::Save appears to be set in stone right now in ADO 2.1.So you
are safe until a beta of the next version of ADO.

Personally, I have struggled with the same problem. I chose the ASP/XMLDOM
route, I did not want to write to disk if I did not have to. Plus with
multiple users, then you have to keep track of these temp files with SESSION
variables, etc. Plus the cost of File I/O as well, as visitors to your web
site increase, performance decreases along with it.

--
Stephen Forte
www.auroradev.com

Quote:

>I am pulling data from a database, converting it to XML, and rendering it
as
>HTML using XSL.  I seem to have (at least) 2 choices when it comes to
>converting the data to XML
>(1) call Recordset::Save with adPersistXML or (2) use an ASP page and the
>XMLDSO to generate XML.

>The first technique requires I create a disk file for the Save, and I deal
>with the XML the Recordset writes.  With the second technique I can invent
>my own XML document type and the XML never needs touch disk.

>My main reservation about using Recordset::Save concerns the XML document
>format.  Is the Recordset generated XML in documented and fixed format, or
>is it an undocumented/unsupported format likely to change?

>Thanks,
>Ed Schiebel



Mon, 17 Sep 2001 03:00:00 GMT
 Persist recordset as XML, or cook XML w/ XMLDSO
I also agree - avoid the disc method.  It also doesn't support hierarchies,
which is why I wrote my own XML generator.

Dave



Quote:
> Using Recordset::Save appears to be set in stone right now in ADO 2.1.So
you
> are safe until a beta of the next version of ADO.

> Personally, I have struggled with the same problem. I chose the ASP/XMLDOM
> route, I did not want to write to disk if I did not have to. Plus with
> multiple users, then you have to keep track of these temp files with
SESSION
> variables, etc. Plus the cost of File I/O as well, as visitors to your web
> site increase, performance decreases along with it.

> --
> Stephen Forte
> www.auroradev.com




- Show quoted text -

Quote:
> >I am pulling data from a database, converting it to XML, and rendering it
> as
> >HTML using XSL.  I seem to have (at least) 2 choices when it comes to
> >converting the data to XML
> >(1) call Recordset::Save with adPersistXML or (2) use an ASP page and the
> >XMLDSO to generate XML.

> >The first technique requires I create a disk file for the Save, and I
deal
> >with the XML the Recordset writes.  With the second technique I can
invent
> >my own XML document type and the XML never needs touch disk.

> >My main reservation about using Recordset::Save concerns the XML document
> >format.  Is the Recordset generated XML in documented and fixed format,
or
> >is it an undocumented/unsupported format likely to change?

> >Thanks,
> >Ed Schiebel



Tue, 18 Sep 2001 03:00:00 GMT
 Persist recordset as XML, or cook XML w/ XMLDSO
I'm currently working on a similar project, and having the same problems
(and a few more;-).
I can't use ASP, so i'm building on temporary XML files pushed to the
clients.

1. can I render my dB-data into a specific XML format ?
2. can someone point/send me a good example of using XMLDSO which renders
also subelements & attributes ?

Thanks,
Arik Barzilay.


Quote:
> I am pulling data from a database, converting it to XML, and rendering it
as
> HTML using XSL.  I seem to have (at least) 2 choices when it comes to
> converting the data to XML
> (1) call Recordset::Save with adPersistXML or (2) use an ASP page and the
> XMLDSO to generate XML.

> The first technique requires I create a disk file for the Save, and I deal
> with the XML the Recordset writes.  With the second technique I can invent
> my own XML document type and the XML never needs touch disk.

> My main reservation about using Recordset::Save concerns the XML document
> format.  Is the Recordset generated XML in documented and fixed format, or
> is it an undocumented/unsupported format likely to change?

> Thanks,
> Ed Schiebel



Sat, 20 Oct 2001 03:00:00 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. ADO 2.5 persisting recordset as XML

2. persisting recordsets to XML

3. Problem Persisting Filtered Recordset to XML DOM

4. Modifing structure for a persisted ADO - XML recordset

5. RecordSet Persisted XML missing namespace

6. Help: ADO 2.5 XML works, ADTG doesn't with persisted recordsets

7. Error persisting XML stream to ADO recordset

8. Recordsets persisted in XML

9. Persisting an ADO Recordset with XML in ASP

10. How do you persist Recordsets to XML?????

11. Problem Persisting Filtered Recordset to XML DOM

12. ADO 2.5 persisting a recordset as XML


 
Powered by phpBB® Forum Software