Lists Home |
Date Index |
- From: "Michael Kay" <M.H.Kay@eng.icl.co.uk>
- To: "Martin Bryan" <firstname.lastname@example.org>, <email@example.com>
- Date: Mon, 15 Dec 1997 16:35:24 -0000
From: Martin Bryan <firstname.lastname@example.org>
To: email@example.com <firstname.lastname@example.org>
Date: 15 December 1997 16:14
Subject: XML interface to Oracle
>I have just been asked by the European Commission Statistics Office if
>anyone has yet hooked an XML parser directly to an Oracle database. (They
>need to transfer large amounts of data between heterogeneous databases ...
Then why specify Oracle in the question?
There are at least two obvious ways of representing a table in XML, the main
is whether to represent data values as attributes or as content. No doubt,
richness of XML, the experts could come up with many less obvious
as well. Using any of the parsers I have looked at, any of these formats
could be trivially
translated into the kind of input formats (e.g. CSV files) that existing
RDBMSs will accept.
Or perhaps by "directly" you want to avoid the intermediate CSV file: well
that's not difficult
either but it's more work and I don't see much benefit in it.
There's a class in the MSXML distribution that gives ADO access to an XML
illustrates what can be done, though of course this is Microsoft
But it all begs the question, what are you (or they) trying to achieve? Is
there really a practical
problem with transferring data between relational databases that XML can
solve? People do
it all the time with various flavours of CSV, so why bother?
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)