db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance J. Andersen" <Lance.Ander...@Sun.COM>
Subject Re: [jira] Created: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations
Date Thu, 04 May 2006 16:28:12 GMT
Just to be clear, this requirement has been part of the J2EE 
specification since 1999.  It is not new.

JDBC 4 is migrating the section from the J2EE spec WRT J2EE jdbc 
requirements to the JDBC spec and future Java EE specs will refer to 
this chapter for requirements.

-lance

Rick Hillegas (JIRA) wrote:
> 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.
>
>   

Mime
View raw message