Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <19939495.1147194725627.JavaMail.jira@brutus>
Date: Tue, 9 May 2006 17:12:05 +0000 (GMT+00:00)
From: "Satheesh Bandaram (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by
 supporting executeQuery() on escaped procedure invocations
In-Reply-To: <4040143.1146759916992.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12378659 ] 

Satheesh Bandaram commented on DERBY-1288:
------------------------------------------

Knut wrote:

> What Derby currently does, is
> 
>   executeQuery:
> 
>     fails whenever a stored procedure is invoked (both embedded and
>   client)

Is that true? According to DERBY-501, executeQuery works for single ResultSet stored procedure for client, but fails for embedded. Since Rick agreed that fixing this would also fix DERBY-501, one of these should be marked a duplicate.

> Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations
> ----------------------------------------------------------------------------------------------
>
>          Key: DERBY-1288
>          URL: http://issues.apache.org/jira/browse/DERBY-1288
>      Project: Derby
>         Type: Improvement

>   Components: JDBC
>     Versions: 10.2.0.0
>     Reporter: Rick Hillegas
>     Assignee: Knut Anders Hatlen
>      Fix For: 10.2.0.0

>
> The following statement raises an error in Derby:
>   statement.executeQuery( "{call foo()}" );
> although this statement works:
>   statement.executeUpdate( "{call foo()}" );
> According to section 6.4 of the latest draft of the JDBC4 Compliance chapter, both statements are supposed to work in order to claim Java EE JDBC Compliance.
> We need to bring Derby into compliance by supporting executeQuery() on escaped procedure invocations.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira