[
https://issues.apache.org/jira/browse/VXQUERY-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611235#comment-14611235
]
Shivani Mall edited comment on VXQUERY-158 at 7/2/15 12:28 AM:
---------------------------------------------------------------
We noticed that queries were not failing because of values being enclosed in {
}. These were working just fine when the final result is enclosed in just one
element node pointable (ENP).
They were failing because now inside an ENP there is another ENP. However,
there is string inside the children chunk of the inner ENP. The check in the
copyElement function never had a case for this. It only expected ENP, TNP PIN
etc.
What I am referring to can be seen here:
https://github.com/apache/vxquery/commit/375dd0e2727d5286006356407ec4549722bb4f98
I will send a pull request once I have tested the XQTS too.
was (Author: shivani):
We noticed that queries were not failing because of values being enclosed in {
}. These were working just fine when the final result is enclosed in just one
element node pointable (ENP).
They were failing because now inside an ENP there is another ENP. However,
there is string inside the children chunk of the inner ENP. However, the check
in the copyElement function, never had a case for this. It only expected ENP,
TNP PIN etc.
What I am referring to can be seen here:
https://github.com/apache/vxquery/commit/375dd0e2727d5286006356407ec4549722bb4f98
I will send a pull request once I have tested the XQTS too.
> Can not read/evaluate { } in queries
> ------------------------------------
>
> Key: VXQUERY-158
> URL: https://issues.apache.org/jira/browse/VXQUERY-158
> Project: VXQuery
> Issue Type: Bug
> Reporter: Shivani Mall
> Assignee: Preston Carman
> Attachments: curly_braces_1.png, curly_braces_2.png
>
>
> Queries that contain nested values enclosed in element constructor function
> fail.
> For example, for the following query the result is missing:
> let $v := "missing"
> return <result><v>{$v}</v></result>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
