Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <13345042.1146768739098.JavaMail.jira@brutus>
Date: Thu, 4 May 2006 18:52:19 +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_12377869 ] 

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

Rick, are you proposing executing only escaped procedures using executeQuery() or ALL SQL procedures? Just wondering why you included 'escaped procedure invocation" in the description specifically. Derby processes all escaped tokens at the server, instead of at client, where it was probably meant to be processed.

Like Dan said, this seems to related to DERBY-501, if not a duplicate of it.

> 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
>      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