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 2007/04/03 01:47:32 UTC
[jira] Created: (DERBY-2516) Network Client allows execution of
callable statement when one of the parameters is not set
Network Client allows execution of callable statement when one of the parameters is not set
-------------------------------------------------------------------------------------------
Key: DERBY-2516
URL: https://issues.apache.org/jira/browse/DERBY-2516
Project: Derby
Issue Type: Bug
Affects Versions: 10.3.0.0
Reporter: Kathey Marsden
Priority: Minor
If the second input parameter is set and the first is not. Client allows execution of the stored procedure. See the following code in LangProcedureTest.java with a reference to this bug.
op.clearParameters();
op.setString(2, "2");
try {
// a not set
op.execute();
fail("FAIL - a not set");
} catch (SQLException sqle) {
assertSQLState("07000", sqle);
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2516) Network Client allows execution of
callable statement when one of the parameters is not set
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2516:
----------------------------------
Component/s: Network Client
> Network Client allows execution of callable statement when one of the parameters is not set
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-2516
> URL: https://issues.apache.org/jira/browse/DERBY-2516
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.3.0.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> If the second input parameter is set and the first is not. Client allows execution of the stored procedure. See the following code in LangProcedureTest.java with a reference to this bug.
> op.clearParameters();
> op.setString(2, "2");
> try {
> // a not set
> op.execute();
> fail("FAIL - a not set");
> } catch (SQLException sqle) {
> assertSQLState("07000", sqle);
> }
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.