[ https://issues.redhat.com/browse/TEIIDSB-192?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-192: ---------------------------------------- The issue with salesforce and mysql is that there taking existing names and subtly changing the behavior - not that it's necessarily bad. Like it was mentioned before we could/should combine mysql/mysql5 on the teiid side anyway and allow the connection version to drive the behavior, just like the other jdbc translators. If you think the other name changes are worth while, then now that it's easier for us to define external sources, we can just add entries for the old names to mitigate migration issues. So really the biggest problem is Salesforce - and to decide what to do with that we should commit to a versioning strategy, then align to that. > Document migration for alias names > ---------------------------------- > > Key: TEIIDSB-192 > URL: https://issues.redhat.com/browse/TEIIDSB-192 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Ramesh Reddy > Priority: Major > Fix For: 1.5.0 > > > Also if we are updating migration utilities we can build in smarts into it. -- This message was sent by Atlassian Jira (v7.13.8#713008)