Bugs item #2124300, was opened at 2008-09-23 12:03
Message generated for change (Comment added) made by stmane
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2124300&group_id=56967
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: PF/compiler
Group: Pathfinder CVS Head
Status: Open
Resolution: Later
Priority: 1
Private: No
Submitted By: Jan Rittinger (tsheyar)
Assigned to: Nobody/Anonymous (nobody)
Summary: PF: error handling for erroneous query incorrect
Initial Comment:
Pathfinder cannot handle stupid queries--queries where the error function is
used in incorrect/unreasonable places--correctly.
This leads to 1.) errors that are optimized away and 2.) compile time problems
as some operators are not able to consume an error operator.
Example for Problem 1: The core representation does not know about side effects
which leads to incorrect optimizations of the following bogus query: '(if (1 eq
1) then error () else 42)/<foo/>' (result is <foo/>).
Example for Problem 2: The algebra does not prune operators sitting on top of
an error operator. For bogus queries such as 'node-name(error("FOO"))' or bug
#2122091 the code generation fails because some assumptions were not met.
For the first problem additional side effect information in the core
respresentation could be a solution. The second problem can be solved by an
algebra rewrite that prunes everything above an error operator (until union
operators representing choices are reached).
----------------------------------------------------------------------
>Comment By: Stefan Manegold (stmane)
Date: 2009-11-15 11:37
Message:
===================================================================
2009/11/15 - stmane: pathfinder/tests/BugTracker/Tests/All,1.146.2.6
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.KO.stable.err,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.KO.stable.out,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.KO.xq,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.OK.stable.err,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.OK.stable.out,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.OK.xq,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.stable.err,1.2.8.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.stable.out,1.2.8.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.xq,1.2.8.1
split test in two to test fixed and still failing part separately;
disabled failing part; please re-enabled once the bug is fixed;
cf.,
ID: 2124300 "PF: error handling for erroneous query incorrect"
https://sourceforge.net/tracker/?func=detail&aid=2124300&group_id=56967&atid=482468
===================================================================
----------------------------------------------------------------------
Comment By: Jan Rittinger (tsheyar)
Date: 2009-02-16 16:12
Message:
Added test.
Problem 2 has been fixed.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2124300&group_id=56967
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
