[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XML Database Decision Tree?

• From: Michael Rys <mrys@m...>
• To: Tom Bradford <bradford@d...>,"Champion, Mike" <Mike.Champion@S...>
• Date: Tue, 30 Oct 2001 18:03:42 -0800

Since Shakespeare plays were not a target scenario for the XML support
in SQL Server 2000, you cannot really do this, unless your Shakespeare
plays are easyily mappable into a relational schema. Then you basically
create the relational schema, use the GUI to map the XML schema to the
relational schema with a few drag and drops, use the bulkload facility
to import it and use the Xpath support to query it.

In Oracle 9i, I assume, you mainly create a table with an XML datatype
and load the Shakespeare document and query it with the extract method.

Best regards
Michael

> -----Original Message-----
> From: Tom Bradford [mailto:bradford@d...] 
> Sent: Tuesday, October 30, 2001 16:38 PM
> To: Champion, Mike
> Cc: PaulT; xml-dev@l...
> Subject: Re:  XML Database Decision Tree?
> 
> 
> On Tuesday, October 30, 2001, at 05:21 PM, Champion, Mike wrote:
> > If by "efficiently" you mean human time rather than 
> computer time, this 
> > can
> > be demonstrated by comparing what it takes to load 
> something like the
> > Shakespeare plays into various DBs of one flavor or another and 
> > performing
> > some XPath queries.  With Tamino (the only one I know how 
> to do this in
> > offhand) the steps are:
> >
> > 1 - load the DTD (or schema) into the Schema editor (tweak content 
> > model to
> > allow 	variations and evolution and define indexes if you must)
> > 2 - Define a DB collection based on that schema  (2 mouse 
> clicks or so)
> > 3 - Use a simple HTML form or a loader script to load the 
> XML data into 
> > the
> > DB
> > 4 - Enter the URL of the database + "_xql=" + an XPath expression
> 
> You big companies and your silly GUI tools.
> 
> I'll follow this up with how it would be done in a dbXML 
> scenario (all 
> of these are typed from the shell):
> 
> 1> dbxmladmin ac -c /db -n newcollection                      
>  # Creates 
> 'newcollection'
> 2> dbxml addmultiple -c /db/newcollection -f ./                # Adds 
> the documents
> 3> dbxml xpath -c /db/newcollection -q <some xpath>  # Queries the 
> collection
> 
>  From a user/admin point of view, the process is brain-dead 
> simple.   The 
> only other steps you might want to take are to add indexes to the 
> collection (best done after a load, just as with RDBSes)
> 
> dbxmladmin ai -c /db/newcollection -n index1 -p elementName
> dbxmladmin ai -c /db/newcollection -n index2 -p elementName@attrName
> dbxmladmin ai -c /db/newcollection -n index3 -p *@attrName
> dbxmladmin ai -c /db/newcollection -n index4 -p elementName@*
> etc...
> 
> -- Tom
> 
> 
> -----------------------------------------------------------------
> 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 elist use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
> 

• Prev by Date: Re: XML Database Decision Tree?
• Next by Date: Re: Re: determining ID-ness in XML
• Previous by thread: Re: XML Database Decision Tree?
• Next by thread: RE: XML Database Decision Tree?
• Index(es):
  • Date
  • Thread