[
https://jira.jboss.org/jira/browse/TEIID-799?page=com.atlassian.jira.plug...
]
Steven Hawkins updated TEIID-799:
---------------------------------
Summary: String to boolean conversion should not throw an exception (was: String
to boolean conversion should throw an exception)
Description: The string to boolean conversion should not throw an exception since that
behavior is not easily ported to sources. Instead both the number to boolean and the
string to boolean conversion should rely on effective boolean value logic. If the value
is null, then null. If the value is false ('0', 'false') then false, else
true. (was: To be more inline with the sql spec. The string to boolean conversion should
throw an exception rather than using the default Boolean.valueOf method when the input
string is not one of 0,1,TRUE,FALSE,UNKNOWN. As it stands the method is inappropriately
marked as non-narrowing and maps any non-true value to false.)
Affects: [Documentation (Ref Guide, User Guide, etc.)]
String to boolean conversion should not throw an exception
----------------------------------------------------------
Key: TEIID-799
URL:
https://jira.jboss.org/jira/browse/TEIID-799
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
The string to boolean conversion should not throw an exception since that behavior is not
easily ported to sources. Instead both the number to boolean and the string to boolean
conversion should rely on effective boolean value logic. If the value is null, then null.
If the value is false ('0', 'false') then false, else true.
--
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