Actions
Bug #2223
closed
Comparing untyped atomics with QNames
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
XPath conformance
Sprint/Milestone:
-
Start date:
2014-11-16
Due date:
% Done:
0%
Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:
Description
This may be a tricky one. The following query returns an error (FORG0001):
{
xs:QName('a:a') = <a>a:a</a>
}
I would have expected "true" as result.
Related issues
Updated by Christian Grün over 9 years ago
Sorry, the query was meant to look like this:
<xml xmlns:a='x'>{
xs:QName('a:a') = <a>a:a</a>
}</xml>/text()
Updated by Michael Kay over 9 years ago
- Category set to XPath conformance
- Priority changed from Low to Normal
Marking this as a duplicate of 2213. It's been fixed on the 9.7 branch but I'm reluctant to do a naive fix for 9.6 because of the cost of saving the full namespace context for every general comparison expression. In 9.7 we're moving towards a design where we always have the namespace context available for every expression and where efficiency relies on the fact that it doesn't change very often.
Updated by Michael Kay over 9 years ago
- Subject changed from Comparing untyepd atomics with QNames to Comparing untyped atomics with QNames
- Status changed from New to Closed
Closed as a duplicate.
Please register to edit this issue
Actions
.