Bugs item #2983860, was opened at 2010-04-08 17:00
Message generated for change (Comment added) made by shcheklein
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2983860&group_id=129076
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: Query Execution
>Group: Sedna (development)
Status: Open
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Yanko Yankulov (core-dumped)
>Assigned to: Ivan Shcheklein (shcheklein)
Summary: seg fault on module & trigger
Initial Comment:
import module namespace ps = "www.packetscale.com/test1";
CREATE TRIGGER "t1" BEFORE INSERT ON doc("someDoc")/* FOR EACH NODE DO {
ps:error(); } &
This statement is accepted by the engine, but the static context holding
module functions is lost after its end, leaving behind PPFunCall object holding
fn_id to destroyed static context. When executing an UPDATE triggering the
----------------------------------------------------------------------
>Comment By: Ivan Shcheklein (shcheklein)
Date: 2010-04-08 18:14
Message:
Yanko, thank you for bug report! This is a known issue with Sedna:
http://thread.gmane.org/gmane.text.xml.sedna/1454 . It requires full
refactoring of dynamic and static contexts.
----------------------------------------------------------------------
Comment By: Yanko Yankulov (core-dumped)
Date: 2010-04-08 17:06
Message:
pressed some buttons too early :) ...
When executing an UPDATE causing the trigger to fire, fn_id is looked up
in current context which hodls undefined function at this fn_id.
Same problem must exist for other static context members -> vars,
namespaces, etc.
Workaround: There's an ugly workaround for this -> use always the same
prolog for every query.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2983860&group_id=129076
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
