Re: Development Trends in Web and Oracle

From: IANAL_VISTA <IANAL_Vista_at_hotmail.com>
Date: Sat, 12 Mar 2005 15:53:42 GMT
Message-ID: <Xns961750505F09ESunnySD@68.6.19.6>

"Hexathioorthooxalate" <ruler_at_removemetoemail.clara.co.uk> wrote in news:1110640998.29701.0_at_iris.uk.clara.net:

> "IANAL_VISTA" <IANAL_Vista_at_hotmail.com> wrote in message
> news:Xns9617425B13F65SunnySD_at_68.6.19.6...

>> Because one can not easily & efficiently search for data stored
>> within XML.

>
>
> Oh yes you can. Remember XMLTYPEs are stored and processed under the
> bonnet on a par with other native Oracle datatypes. The data is
> stored relationally using with little performance impact if
> appropriately indexed. The most important message to get across is
> that this is neither an inefficient addin nor is the XML being
> searched with LIKE %whatever% or doing full table scans (unless you
> have implemented it incorrectly and here the argument stands equally
> for the relational model too). The XML is shredded upon insert and
> stored relationally; the required XML is reconstituted upon SELECT.
>
> The select statement below is how easy it can be to select data. The
> searching can be as easy as the XPATH expression.
> Regards
> Hex
>
>
> Eg (don't have access to db at the moment but it really is as trivial
> as below). Search out more examples with Google or in the Oracle docs.
> Hex

A shovel is a great tool for creating a hole in the ground, but only when the "correct" end comes into contact with the Earth.

When your only tool is a hammer, all problems are viewed as nails.

XML is NOT an efficient data storage & retrevial tool/mechanism. The fact that it can be used to do so, does not imply it should be used for data storage & retrevial when better alternatives exist. Received on Sat Mar 12 2005 - 09:53:42 CST