[
Lists Home |
Date Index |
Thread Index
]
Title: RE: [xml-dev] save XML into database
A BLOB is a Binary Long Object and is not suitable for XML.
You either want to store it in a CLOB, which is a character long object, if you want no structure controls, or if you use Oracle then there is an XMLTYPE. It is possible to define either a whole table as an XMLTYPE or an individual column. I would suggest not using Access, I haven't used the XML features in SQL Server, but Oracle's offering is fairly comprehensive especially if you go for Oracle 10g release 2.
If you want to formalise your XML structures then Oracle allows you to register an XML Schema in the database and it will automatically generate your table and type structures for you. Oracle 10g release 2 now allows the schemas to be evolved, which in earlier versions if you wanted to change your scheme then you had to export all your XML files and then reimport once the schema had been changed.
The Oracle Technology Network site has useful information and downloadable demos
http://www.oracle.com/technology/tech/xml/xmldb/index.html
Regards,
Jon
-----Original Message-----
From: jj long [mailto:longjingjun@yahoo.com.cn]
Sent: 28 October 2005 10:48
To: Li Yuejiong(John); jim.fuller@ruminate.co.uk
Cc: xml-dev@lists.xml.org
Subject: RE: [xml-dev] save XML into database
hi John,
I think basicly you can save the xml content as blob
in database. It does not have any difference with
other files like doc,pdf from database point of view.
The methods of accessing xml data in db are vary from
vender even many databases support xml. Perhaps store
xml content as blob is a good choice since you
mentioned you are using three different database now.
Long
--- "Li Yuejiong(John)" <john_li@macrosynergy.com>
wrote:
> HI Jim,
>
> I know it cannot be answered in one mail. So I ask
> for a guildline, not
> a solution. About XML DB, I cannot use them, because
> my develop
> environement is SQL Server, Oracle or Access.
>
> Thanks,
> John
>
> -----Original Message-----
> From: James Fuller
> [mailto:jim.fuller@ruminate.co.uk]
> Sent: Friday, October 28, 2005 3:37 PM
> To: Li Yuejiong(John)
> Cc: xml-dev@lists.xml.org
> Subject: Re: [xml-dev] save XML into database
>
> Li Yuejiong(John) wrote:
>
> >Hi,
> >
> >I want to save XML file into database, eg SQL
> Server, Oracle or maybe
> >Access. I am a newbie of database, so is there any
> guideline of such a
> >task?
> >
> >
> your question is quite broad in scope...I would
> select a specific
> database then google on that..
>
> as a side note I would suggest bypassing all this
> together and try out a
> native XML DB,
>
> http://exist.sourceforge.net is the best of the open
> source
> offerings....being surprisingly performant and
> loaded with features.
>
> gl, Jim Fuller
>
>
>
>
-----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager:
> <http://www.oasis-open.org/mlmanage/index.php>
>
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>
************************************************************************
DISCLAIMER
The information contained in this e-mail is confidential and is intended
for the recipient only.
If you have received it in error, please notify us immediately by reply
e-mail and then delete it from your system. Please do not copy it or
use it for any other purposes, or disclose the content of the e-mail
to any other person or store or copy the information in any medium.
The views contained in this e-mail are those of the author and not
necessarily those of Admenta UK Group.
************************************************************************
| 