This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1896 - Consistency between date/time overflow and numeric overflow
Summary: Consistency between date/time overflow and numeric overflow
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Ashok Malhotra
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-26 17:26 UTC by Don Chamberlin
Modified: 2005-09-29 12:55 UTC (History)
0 users

See Also:

Attachments

Description Don Chamberlin 2005-08-26 17:26:48 UTC 
In bug 1489, we decided that casting from a string to a numeric type is treated 
as an overflow/underflow (e.g., FOAR0002, "Numeric operation 
overflow/underflow") if the resulting value is too big/small. But in casting 
from a string to a date/time/duration it is also possible that the value is too 
big/small to represent. The current F&O spec treats this as FORG0001, "Invalid 
value for cast/constructor". For consistency, should we change the error code 
for this condition to FODT0001 ("Overflow in date/time arithmetic") or FODT0002 
("Overflow in duration arithmetic")?
Comment 1 Ashok Malhotra 2005-09-27 15:35:37 UTC 
The WGs decided on 9/27 to fix this bug by adopting Don Chamberlin's
recommendation: "...in casting 
from a string to a date/time/duration it is also possible that the value is too 
big/small to represent. The current F&O spec treats this as FORG0001, "Invalid 
value for cast/constructor". For consistency, should we change the error code 
for this condition to FODT0001 ("Overflow in date/time arithmetic") or FODT0002 
("Overflow in duration arithmetic")?"