[
https://jira.jboss.org/jira/browse/TEIID-744?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-744.
----------------------------------
Resolution: Done
Addressing in 6.2 since it would be best to not have unpredictable results. Also ensured
that all lossy conversions are handled as explicit. We'll come up with better
stories around inversion when it becomes a requested feature.
Inversion of convert(string, ...) and parseXXX(string, ...) is not
always possible.
-----------------------------------------------------------------------------------
Key: TEIID-744
URL:
https://jira.jboss.org/jira/browse/TEIID-744
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
The parsing routines for date and numeric types from string allow for non-canonical
string forms. Inverting the convert or parse assumes that the format matches exactly (no
additional trailing 0's for example) and there is no leading/trailing ws.
--
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