OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re[2]: SQL instead of XQuery


JS> Your objections seem to be about collections of homogeneous documents
JS> being the unit of storage - but an XML database doesn't have to work
JS> that way.

In mentioned other way,
what is advantage of XML-database before relational database ?
What is the secret sauce (raisin in russian language) of usage of XML ?

JS> To relate things to the relational model ...
JS> to think of each document in a collection as a row in a table...
JS> [or] to think of each document as a table in a database.

Are xml-elements in documents predictable ? repeated ?
Or it's not depends of this parameter ?

JS> collections of documents ... clearly offer a superset
JS> of the functionality in the relational model

Possibility to save unique, not predicted xml-element is
single positive difference from table/attribute databases.
Obviously it's not that you implied.
So what is 'superset of functionality' in your interpretation ?

This difference can be voided by entering auto-creating and
auto-altering of table in table/attribute databases.

JS> and are therefore capable
JS> of naturally expressing far more complex structures.

Examples, please, of these more complex structures !!
Written in xml-elements, please.

Dmitry Turin
HTML6     (6. 5.3)  http://html60.euro.ru
SQL5      (5.11.1)  http://sql50.euro.ru
Unicode7  (7. 2.1)  http://unicode70.euro.ru
Computer2 (2. 0.2)  http://computer20.euro.ru

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS