You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2011/02/14 22:11:57 UTC
[jira] Updated: (DERBY-2512) Network client should not allow
prepare of a stored procedure with an output parameter using a
PreparedStatement
[ https://issues.apache.org/jira/browse/DERBY-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-2512:
----------------------------------
Issue & fix info: [Newcomer, Repro attached]
Urgency: Low
Bug behavior facts: [Embedded/Client difference]
Labels: derby_triage10_8 (was: )
Triage for 10.8
> Network client should not allow prepare of a stored procedure with an output parameter using a PreparedStatement
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2512
> URL: https://issues.apache.org/jira/browse/DERBY-2512
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.3.1.4
> Reporter: Kathey Marsden
> Priority: Minor
> Labels: derby_triage10_8
>
> In converting procedure.java I found this issue. Network Client should not allow a statement to be prepared using a PreparedStatement object if it has an output parameter. See the following case and reference to this bug in the converted LangProcedureTest.java
> PreparedStatement ps = conn.prepareStatement("CALL OP1(?, ?)");
> fail("FAIL prepare succeeded on OUT param with PreparedStatement");
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira