[teiid-issues] [JBoss JIRA] (TEIID-2247) API changes in point release

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-2247:
---------------------------------------

These are all internal apis and will most definitely change in point releases to accommodate features.  It is a long standing issue to get Teiid Designer off of Teiid's language objects.

The TeiidRuntimeException constructors were removed since they no longer followed usage patterns in Teiid, but can be added back if needed.

The modifications to RaiseErrorStatement and CreateProcedureCommand will not be undone.  The change in RaiseErrorStatement reflects that it now represents a RAISE statement rather than an ERROR statement.  Also the logic to determine the results command was not generally correct as there can be many results commands.  If you want the results set columns post resolve, then use the getResultSetColumns method.
                
> API changes in point release
> ----------------------------
>
>                 Key: TEIID-2247
>                 URL: https://issues.jboss.org/browse/TEIID-2247
>             Project: Teiid
>          Issue Type: Bug
>    Affects Versions: 8.2
>            Reporter: Paul Richardson
>            Assignee: Steven Hawkins
>             Fix For: 8.2
>
>
> Updated teiid designer 8.0 (unreleased) to 8.2.Alpha2 jars.
> API changes have occurred between 8.1 and 8.2. Are the following changes essential and could they be reverted and deprecated until 9.0?
> * org.teiid.query.sql.proc.RaiseErrorStatement renamed to org.teiid.query.sql.proc.RaiseStatement
> * org.teiid.core.TeiidRuntimeException
>  ** Constructor(String, String) visibility narrowed
>  ** Constructor(Exception, String) removed
> * org.teiid.query.sql.proc.CreateProcedureCommand
>  * Removal of getResultsCommand() method

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira