[
https://jira.jboss.org/jira/browse/TEIID-744?page=com.atlassian.jira.plug...
]
Steven Hawkins updated TEIID-744:
---------------------------------
Summary: Inversion of convert(string, ...) and parseXXX(string, ...) is not
always possible. (was: Inversion of convert(string, ...) is not always possible.)
Fix Version/s: 6.3.0
(was: 6.2.0)
Description: 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. (was: The parsing routines for date and numeric types from string
allow for non-canonical string forms. Inverting the convert assumes that the standard
toString format must be used.)
Pushing to 6.3 for now, since this is not a regression and we may have a better story
around pushing down the parse function.
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.3.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