Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Re: [offtopic] Re: SQL instead of XQuery

From: Jonathan Robie <jonathan.robie@------.--->
To: andrzej@-------.---
Date: 2/8/2008 1:21:00 PM
Andrzej Jan Taramina wrote:
> Dimitry:
>   
>> Speach goes about query language on slides,
>> instead of algorithms of engine.
>>     
>
> I disagree.  SQL works against relational databases.  XQuery goes against XML 
> and XML databases, so the comparison of SQL vs XQuery drags in the topic of 
> what storage mechanism to use as well.
>   

The people who define SQL, H2, decided to support XQuery for querying 
XML. They started by trying to extend SQL, there have been many 
proposals to do that, but they concluded that supporting XQuery from 
within SQL was important.

Dimitry's SQL5 is not a language that H2 would recognize as SQL.

I think the industry has been adopting SQL for querying relational data 
and XQuery for querying XML. These languages have been widely perceived 
as good languages for the tasks they were designed for. Since these are 
the standards, and they do the job well, they are likely to remain in 
place.

Who is actually using SQL5? Is anyone besides Dimitry pushing it?

Jonathan


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent