[teiid-issues] [JBoss JIRA] Commented: (TEIID-105) MySQL capabilities should be made specific to version 4/5

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Mon Apr 20 16:31:22 EDT 2009


    [ https://jira.jboss.org/jira/browse/TEIID-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463281#action_12463281 ] 

Steven Hawkins commented on TEIID-105:
--------------------------------------

Yes it's still valid.  We have already downgraded the translator to only support 4.x.  If we can choose not to make any changes to the translator, we should be sure to call it a MySQL version 4 connector.  The intent of the issue was to really clarify version support.  It could be a separate issue to create the 5.x translator.

> MySQL capabilities should be made specific to version 4/5
> ---------------------------------------------------------
>
>                 Key: TEIID-105
>                 URL: https://jira.jboss.org/jira/browse/TEIID-105
>             Project: Teiid
>          Issue Type: Bug
>          Components: JDBC Connector
>    Affects Versions: 6.x
>            Reporter: Steven Hawkins
>             Fix For: 6.1.0
>
>
> Defect Tracker #24746: The current mysql capabilities seem to have been written for version 5 (it initially included support for timestampdiff).  The support for 4.x should be specifically refined or specifically removed from the docs.  4.x goes completely  eol by the end of 2009, so it's unlikely many customers would care if this were done for 5.5.1.
> see also http://www.mysql.com/company/legal/lifecycle/#calendar

-- 
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