[teiid-issues] [JBoss JIRA] (TEIID-5130) Document/refine behavior of treating result parameter as the first parameter

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-5130.
-----------------------------------
    Fix Version/s: 9.3.5
       Resolution: Done


Added more backward compatibility checks to the ws translator.

This commit enforces that the result param must be first in the procedure.  This is enforced by the property org.teiid.resultAnyPosition which default to false for 10.0 - which is a narrow breaking change, so it's documented how the legacy behavior can be achieved.

For 9.3.x org.teiid.resultAnyPosition defaults to true, to keep the old behavior.

> Document/refine behavior of treating result parameter as the first parameter
> ----------------------------------------------------------------------------
>
>                 Key: TEIID-5130
>                 URL: https://issues.jboss.org/browse/TEIID-5130
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 9.3.5, 10.0
>
>
> DDL and metadata import make the assumption that the return parameter is the first in the underlying metadata (in part to ensure support of varargs), but we still allowed the result parameter to appear anywhere in the parameter list as to maintain backwards compatibility with legacy/Designer ddl.  However in index metadata there is slightly different behavior in that the result parameter remains in it's original position.
> We need to clarify this behavior - more documentation, enforce/validate that the result parameter is first in ddl, or perform the same reordering for index metadata.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)