zorba-coders team mailing list archive

[Federico Cavalieri <854723@xxxxxxxxxxxxxxxxxx>]

The following expression raises a similar error, due to the same
assumption:

import schema namespace s = "http://www.xqdoc.org/1.0";;
import module namespace schema = "http://www.zorba-xquery.com/modules/schema";;

variable $hostInfo :=<xqdoc xmlns="http://www.xqdoc.org/1.0";>
    <control>
        <date>TS4J5UJ</date>
        <version>N/A</version>
    </control>
    <module type="library">
        <uri>DGQEb8Q</uri>
    </module>
</xqdoc>;


schema:validate-in-place($hostInfo);
replace node $hostInfo//*:date/node()[1] with <?processinginstruction aaa?>;
$hostInfo


Raises:
Zorba Internal Fatal Error in /zorba/trunksrc/src/store/naive/pul_primitives.cpp:489:
"target->getChild(0)->getNodeKind() == store::StoreConsts::textNode": condition failed
Aborted


** Description changed:

- This bug is due to the same incorrect assumption reported in bug 854688. 
- Invoking schema:validate-in-place creates several UpdSetElementType operations. Their apply method expects that if a node has a typedvalue it also contains a single node with text type. This is not true in the following example.
+ This bug is due to the same incorrect assumption reported in bug 854688.
+ Invoking schema:validate-in-place creates several UpdSetElementType operations. Their apply method expects that if a node has a typedvalue it also contains a single node with text type. This is not true in the following example, which raises:
+ 
+ Zorba Internal Fatal Error in /zorba/trunksrc/src/store/naive/pul_primitives.cpp:488:
+ "target->numChildren() == 1": condition failed
+ Aborted

-- 
You received this bug notification because you are a member of Zorba
Coders, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/854723

Title:
  Internal Fatal Error with validate-in-place

Status in Zorba - The XQuery Processor:
  New

Bug description:
  This bug is due to the same incorrect assumption reported in bug 854688.
  Invoking schema:validate-in-place creates several UpdSetElementType operations. Their apply method expects that if a node has a typedvalue it also contains a single node with text type. This is not true in the following example, which raises:

  Zorba Internal Fatal Error in /zorba/trunksrc/src/store/naive/pul_primitives.cpp:488:
  "target->numChildren() == 1": condition failed
  Aborted

To manage notifications about this bug go to:
https://bugs.launchpad.net/zorba/+bug/854723/+subscriptions