[teiid-issues] [JBoss JIRA] Commented: (TEIID-745) Ensure string parsing routines are consistent
Steven Hawkins (JIRA)
jira-events at lists.jboss.org
Mon Aug 31 16:31:23 EDT 2009
[ https://jira.jboss.org/jira/browse/TEIID-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12483763#action_12483763 ]
Steven Hawkins commented on TEIID-745:
--------------------------------------
These changes are unnecessary for the parseXXX methods, since their impls are not guided by the SQL spec.
> Ensure string parsing routines are consistent
> ---------------------------------------------
>
> Key: TEIID-745
> URL: https://jira.jboss.org/jira/browse/TEIID-745
> Project: Teiid
> Issue Type: Quality Risk
> Components: Common, Query Engine
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 6.2.0
>
>
> String parsing strictness varies depending upon whether a convert or a parse function is used. In short we should for all parse routines:
> 1. Perform a trim prior to parsing (double and float converts already do this implicitly)
> 2. Use all non-whitespace characters in the parse string - the DateFormat, NumberFormat, and most of the convert methods allow for junk to appear after a successful parsing.
> 3. Time/Date/Timestamps should use non lenient parsing to disallow dates that are out of range, i.e. 2007-13-35
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the teiid-issues
mailing list