Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Thu, 04 May 2006 13:01:34 -0400
From: "Lance J. Andersen" <Lance.Andersen@Sun.COM>
Subject: Re: [jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance
 by
 supporting executeQuery() on escaped procedure invocations
In-reply-to: <22600630.1146761904203.JavaMail.jira@brutus>
Sender: Lance.Andersen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <445A336E.8090006@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_LDHV5xIK2H5Yhe8opDVM/g)"
References: <22600630.1146761904203.JavaMail.jira@brutus>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)

This is a multi-part message in MIME format.

--Boundary_(ID_LDHV5xIK2H5Yhe8opDVM/g)
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 7BIT


Daniel John Debrunner (JIRA) wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377843 ] 
>
> Daniel John Debrunner commented on DERBY-1288:
> ----------------------------------------------
>
> What's the required behavior when a update count or multiple result sets are returned?
>   
the expected behavior would be no different then what u do a Statement 
object today
> If multiple result sets are returned when should any error be thrown, before the execution starts or once the system detects that multiple result sets are returned?
>   
This would probably be implementation defined depending on the mechanism 
being used.
> A lot of existing discussion has been in DERBY-501
>
>   
>> 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.
>>     
>
>   

--Boundary_(ID_LDHV5xIK2H5Yhe8opDVM/g)
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Daniel John Debrunner (JIRA) wrote:
<blockquote cite="mid22600630.1146761904203.JavaMail.jira@brutus"
 type="cite">
  <pre wrap="">    [ <a class="moz-txt-link-freetext" href="http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377843">http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377843</a> ] 

Daniel John Debrunner commented on DERBY-1288:
----------------------------------------------

What's the required behavior when a update count or multiple result sets are returned?
  </pre>
</blockquote>
the expected behavior would be no different then what u do a Statement
object today<br>
<blockquote cite="mid22600630.1146761904203.JavaMail.jira@brutus"
 type="cite">
  <pre wrap="">
If multiple result sets are returned when should any error be thrown, before the execution starts or once the system detects that multiple result sets are returned?
  </pre>
</blockquote>
This would probably be implementation defined depending on the
mechanism being used.<br>
<blockquote cite="mid22600630.1146761904203.JavaMail.jira@brutus"
 type="cite">
  <pre wrap="">
A lot of existing discussion has been in DERBY-501

  </pre>
  <blockquote type="cite">
    <pre wrap="">Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations
----------------------------------------------------------------------------------------------

         Key: DERBY-1288
         URL: <a class="moz-txt-link-freetext" href="http://issues.apache.org/jira/browse/DERBY-1288">http://issues.apache.org/jira/browse/DERBY-1288</a>
     Project: Derby
        Type: Improvement
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">  Components: JDBC
    Versions: 10.2.0.0
    Reporter: Rick Hillegas
     Fix For: 10.2.0.0
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">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.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

--Boundary_(ID_LDHV5xIK2H5Yhe8opDVM/g)--