5694 2008-05-16 10:07:41 +0000 K2-SeqExprCast-22,78,90 may raise FOAR0002 2008-05-21 20:22:45 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite unspecified PC Windows XP CLOSED FIXED P2 normal --- 1 vano_msu frans.englich public-qt-comments oldest_to_newest 20139 0 vano_msu 2008-05-16 10:07:41 +0000 I believe K2-SeqExprCast-22,78,90 may raise FOAR0002 due to the following rule (F&O 11.1.7): "In casting to numerics, if the value is too large or too small to be accurately represented by the implementation, it is handled as an overflow or underflow as defined in 6.2 Operators on Numeric Values." 20166 1 frans.englich 2008-05-20 10:54:21 +0000 Added FOAR0002 to K2-SeqExprCast-22. Regarding K2-SeqExprCast-78 and K2-SeqExprCast-90: these doesn't run into implementation defined limits, they are invalid values no matter what. For that reason they expect FORG0001. Does this sound correct? 20175 2 vano_msu 2008-05-20 17:06:41 +0000 I'm not sure actually. It seems that xs:unsignedLong, xs:long. xs:integer built in datatypes don't have pattern facets defined by default. They have only restrictions through maxInclusive/minInclusive and similar facets. So, in K2-SeqExprCast-78 for example we follow the specification (F&O 17.5): ----------------------------------- "... Casting across the type hierarchy is logically equivalent to three separate steps performed in order. Errors can occur in either of the latter two steps. ... 2.Cast the value to the primitive type of TT, as described in 17.1 Casting from primitive types to primitive types." ----------------------------------- It means we should perform the following casting operation in the intermediate step: "-9223372036854775809" cast as xs:integer which may raise FOAR0002. 20200 3 frans.englich 2008-05-21 11:13:31 +0000 Should be fixed in CVS. 20208 4 vano_msu 2008-05-21 20:22:45 +0000 Thanks!