db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations
Date Thu, 04 May 2006 16:25:16 GMT
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


Mime
View raw message