Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <281555725.1246904475000.JavaMail.jira@brutus>
Date: Mon, 6 Jul 2009 11:21:15 -0700 (PDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2810) getParameterType behavior is different
 in Embedded and Network Client when set by registerOutParameter
In-Reply-To: <12902445.1181724266503.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rick Hillegas updated DERBY-2810:
---------------------------------

         Component/s: JDBC
    Issue & fix info: [Repro attached]
             Urgency: Normal

Triaged for 10.5.2: assigned normal urgency, noted that a repro is available.

> getParameterType behavior is different in Embedded and Network Client when set by registerOutParameter
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2810
>                 URL: https://issues.apache.org/jira/browse/DERBY-2810
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.3.1.4
>         Environment: Fedora Core release 6
>            Reporter: Ramin Moazeni
>
> Description:
> =========
> The behavior of getParameterType is different in embedded and network client 
> as shown by the following code snippet:
> --------------------------------------------------------------------------------------------------------
> public void testCallableStatementReturnedScale () throws SQLException {
>                 Statement stmt = createStatement();
>                 stmt.executeUpdate("create procedure dummy_numeric_Proc(out a NUMERIC(30,15), out b NUMERIC(30,15)) language java parameter style java external name 'org.apache.derbyTesting.functionTests.tests.jdbcapi.parameterMetaDataJdbc30.dummy_numeric_Proc'");
>                 CallableStatement cs = prepareCall("CALL dummy_numeric_Proc(?,?)");
>                 cs.registerOutParameter(1, Types.NUMERIC);
>                 cs.registerOutParameter(2, Types.NUMERIC,15);
>                 cs.execute();
>                
>                 int numParam = cs.getParameterMetaData().getParameterCount();
>                 for (int i=1; i<=numParam; i++) {
>                            System.out.println("getParameterType: " + cs.getParameterMetaData().getParameterType(i));
>                 }
>                 cs.close();
>         }
> --------------------------------------------------------------------------------------------------------
> Results:
> ======
> * Testing with org.apache.derby.jdbc.ClientDriver
> getParameterType: 3 <-------Types.DECIMAL
> * Testing with org.apache.derby.jdbc.EmbeddedDriver
> getParameterType: 2 <-------Types.NUMERIC

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