db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2786) Behaviour of inout parameters in Embedded and Network client is different if parameters are set but the CallableStatment is not executed.
Date Mon, 06 Jul 2009 17:45:14 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-2786:
---------------------------------

    Component/s: JDBC
        Urgency: Normal

Triaged for 10.5.2: Assigned normal urgency.

> Behaviour of inout parameters in Embedded and Network client is different if parameters
are set but the CallableStatment is not executed.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2786
>                 URL: https://issues.apache.org/jira/browse/DERBY-2786
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.3.1.4
>         Environment: Operating Systems: Fedora Core release 6 
>            Reporter: Ramin Moazeni
>            Priority: Minor
>         Attachments: Main.java
>
>
> The behavior of embedded and network client is different in for inout
> parameters if parameters are set but the CallableStatment is not executed.  
> For detailed description of this issue on derby-dev, refer to
> http://www.nabble.com/Regarding-DERBY-2658%3A-Converting-jdbcapi-parameterMetaDataJdbc30.java-to-JUnit-tf3882490.html#a11003923

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message