Feature Requests item #2877036, was opened at 2009-10-12 14:43
Message generated for change (Comment added) made by tsheyar
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482471&aid=2877036&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: Pathfinder - runtime
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Roberto Cornacchia (cornuz)
Assigned to: Nobody/Anonymous (nobody)
Summary: PF: more useful error reports

Initial Comment:
Currently, runtime errors are reported as an error code + textual description.
Often this is not enough, especially because the error refers to algebra 
expressions that could have been generated by the compiler, so they are hard to 
find in the query text. 
Example:

ERROR = !ERROR: err:FORG0003, fn:zero-or-one called with a sequence containing 
more than one item.

With enough experience, most of the times it is possible to find which 
expression in the original query generated this,
although there is no explicit zero-or-one() call. However, when the query is 
non-trivial, this becomes a real pain.

If it is too hard to trace back the exact line in the query text (which should 
be possible anyway), a printout of the algebra expression being evaluated, 
whith some context around, would certainly help to quickly spot the error.


----------------------------------------------------------------------

Comment By: Jan Rittinger (tsheyar)
Date: 2009-10-13 00:03

Message:
As far as I can oversee almost nobody would understand the algebra plan in
a textual representation. In most cases it's not easy to digest.

The best solution would be to give an estimate position with respect to
the input query. Currently we loose the position information before the
translation to our XQuery Core representation -- probably because due to
rewrites positions might be misleading. Necessary changes to make
'assumptions on the position' would include making the Core representation
location-aware, keeping positions over rewrites, and incorporating location
information in the core2algebra translation...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482471&aid=2877036&group_id=56967

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs

Reply via email to