W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2006

[Bug 2796] [Update] updating nodes, then returning values computed from them

From: <bugzilla@wiggum.w3.org>
Date: Sun, 23 Jul 2006 23:19:10 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1G4nE6-0005Vl-Ds@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2796


tony.santangelo@periphron.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tony.santangelo@periphron.ne
                   |                            |t




------- Comment #2 from tony.santangelo@periphron.net  2006-07-23 23:19 -------
I'm distressed to find that the Working Draft of 11 July 2006 still does not
address this issue. The current spec seems to make it impossible, for example,
to express web application logic in XQuery. If even top-level queries must
either return a value OR perform an update, but never both, then *something*
(other than XQuery) is going to have to co-ordinate the response to requests
that involve updates. And the revolution is once again deferred.

The update model currently used in eXist, a native XML DBMS, 
(http://exist.sourceforge.net) has the characteristic described in Comment #1:
update expressions evaluate to the empty sequence. This tool drastically
reduces the pain of web development.

Please allow XQuery (with Update) to be a programming language, not just a
query language.
Received on Sunday, 23 July 2006 23:19:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:29 UTC