[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2429: ---------------------------------------- To shed light on Designer's support of Teiid versions..... My understanding of the Teiid Server/runtime version support is that it's based on being able to consume artifacts from older versions as well as the latest. I'm guessing there are instances where older artifacts may not be "fully" compatible with newer Teiid runtimes, but I understand your goal is backward support. Designer's requirement is to support the development and maintenance of artifacts for different Teiid target runtimes. This requirement exists so users can load older artifacts into their workspace, connect to a newer server version and if there are any particular changes in constructs/SQL or SQL validation that have changed, Designer will point out those issues and the user can fix them. Designer couldn't do that if it only supported the latest version of Teiid. Supporting the move from Teiid 7.x to 8.x probably posed the largest challenge, but even Teiid 8.x minor releases have impacted SQL constructs and validation that needed to get tracked/addressed. For Designer 9.1 we'll be trying to add an option to relax the version restriction for Teiid version so users can "disable" our basic version-support and proceed at their own risk. As we move into our Komodo release, we'll hoping to drop specific support for older server versions because migration will entail converting old artifacts into the latest Teiid DDL/VDB structures. -- This message was sent by Atlassian JIRA (v6.3.11#6341)