Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: SV: SV: Schema help

From: noah_mendelsohn@--.---.---
To: "Michael Kay" <mike@--------.--->
Date: 11/17/2005 10:44:00 AM
Michael Kay writes:

> I would resist this kind of thinking. SQL was successful because it 
> put functionality first, and left implementors to devise 
> optimisation strategies.

I am sympathetic to this as one side of the tradeoff, but I don't think it 
entirely settles the question.  The Principle of Least Power [1] suggests 
that we don't want to use a bulldozer when a simple hammer will do.  Even 
SQL succeeds in part because it is declarative and ammenable to 
optimization in ways that a more general or more imperative language might 
not be.  I agree that we should not necessarily design the language around 
particular optimizations, but I do believe it's important to convince 
ourselves that it is likely to be optimizable.

Noah

[1] http://www.w3.org/DesignIssues/Principles.html#PLP

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------





From brs@i... Fri Nov 18 08:34:35 2005
Received: from lisa.w3.org ([128.


transparent
Print
Mail
Digg
delicious
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