[
https://jira.jboss.org/jira/browse/TEIID-352?page=com.atlassian.jira.plug...
]
Steven Hawkins updated TEIID-352:
---------------------------------
Original Estimate: 3 days
Remaining Estimate: 3 days
Fix Version/s: 6.0.0
(was: 6.1.0)
Description: SQLTranslators are extremely cumbersome and not well documented.
We need something much more like Hibernate's dialect. We should have a single
Translator class that replace ResultsTranslator, SQLTranslator, and SQLConversion visitor.
(was: SQLTranslators are extremely cumbersome and not well documented. We need something
much more like Hibernate's dialect. Also the time literal for Access/SQLServer is
incorrect and the limit with set op will also fail for Access/SQLServer.)
Affects: [Documentation (Ref Guide, User Guide, etc.),
Compatibility/Configuration, Release Notes] (was: [Documentation (Ref Guide, User Guide,
etc.), Release Notes])
Complexity: High (was: Medium)
JDBC SQLTranslator issues
-------------------------
Key: TEIID-352
URL:
https://jira.jboss.org/jira/browse/TEIID-352
Project: Teiid
Issue Type: Sub-task
Components: JDBC Connector
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.0.0
Original Estimate: 3 days
Remaining Estimate: 3 days
SQLTranslators are extremely cumbersome and not well documented. We need something much
more like Hibernate's dialect. We should have a single Translator class that replace
ResultsTranslator, SQLTranslator, and SQLConversion visitor.
--
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