[teiid-issues] [JBoss JIRA] Resolved: (TEIID-86) registering of CallableStatement out parameters should be used

[Steven Hawkins (JIRA)]

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

Steven Hawkins resolved TEIID-86.
---------------------------------

    Fix Version/s:     (was: 9.x)
       Resolution: Partially Completed


Changes to stored procedure handling largely account for this issue.  If a user has a query with both return and out parameters we will appropriately omit the return parameter if it is not asked for.  

There are two remaining reasons we should consider using out parameter information:
1. to have better parameter indexing logic TEIID-98
2. to enforce what getters can be used.

Neither of these is particularly high priority.

> registering of CallableStatement out parameters should be used
> --------------------------------------------------------------
>
>                 Key: TEIID-86
>                 URL: https://issues.jboss.org/browse/TEIID-86
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 9.x
>            Reporter: Steven Hawkins
>            Priority: Minor
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> The registering of CallableStatement out (out, inout, return) parameters should be used to 
> 1. help resolve the procedure - if there is a type mismatch or a parameter requested that doesn't exist an exception should be thrown.  
> 2. determine what out parameters the driver should know about.  currently the driver is supplied with all out values regardless of how many are registered.  this means that the user may not get the right value if the statement does not fully specifier all out parameters.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira