XML database: Difference between revisions

Revision as of 19:03, 11 May 2020

Revision as of 18:07, 21 November 2020

Line 17:

* Provides a solution for [[Object-relational impedance mismatch]]<ref>[NoSQL Distilled: A Brief Guide to the Emerging World of Polyglot Persistence. Addison-Wesley Educational Publishers Inc, 2009] {{ISBN|978-0321826626}}</ref>

Steve O'Connell gives one reason for the use of XML in databases: the increasingly common use of XML for [[transport layer|data transport]], which has meant that "data is extracted from databases and put into XML documents and vice-versa".<ref name=oconnell2005>{{cite report|author=O'Connell, Steve|work=Advanced Databases Course Notes|title="Section 9.2"|type=Syllabus|date=2005|publisher=[[University of Southampton]]|___location=Southampton, England}}</ref>{{update inline|date=March 2015}} It may prove more efficient (in terms of conversion costs) and easier to store the data in XML format. In content-based applications, the ability of the native XML database also minimizes the need for extraction or entry of metadata to support searching and navigation.

== XML enabled databases ==

Line 156:

== Data-centric XML datasets ==

For data-centric XML datasets, the unique and distinct keyword search method, namely, XDMA<ref>{{Cite journal|lastlast1=Selvaganesan|firstfirst1=S.|last2=Haw|first2=Su-Cheng|last3=Soon|first3=Lay-Ki|title=XDMA: A Dual Indexing and Mutual Summation Based Keyword Search Algorithm for XML Databases|journal=International Journal of Software Engineering and Knowledge Engineering|language=en-US|volume=24|issue=4|pages=591–615|doi=10.1142/s0218194014500223|year=2014}}</ref> for XML databases is designed and developed based on dual indexing and mutual summation.

== References ==