Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: domain of msatoor@gmail.com designates
 64.233.184.198 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=gblN2ZjCozAkvQK3Ib3Ult3M2S+xyMYnxvmDHI92vnBgXqTUMtHVik+kBs7M28m5G0Xk2UMfUeVFcF46mgZ3CdXG5ADqtD+7b670kLyjse1hi1rI2Wk/HGBdMqNsiKRXgDD1e6oWRPdaKunCPOPJq4NCXzJfXSCuEqunCZu0S8o=
Message-ID: <d9619e4a0505101149143bfcbd@mail.gmail.com>
Date: Tue, 10 May 2005 11:49:32 -0700
From: Mamta Satoor <msatoor@gmail.com>
Reply-To: Mamta Satoor <msatoor@gmail.com>
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [jira] Updated: (DERBY-227) Reference manual has incorrect
 information for supported resultset types for prepareCall JDBC api
In-Reply-To: <1216407538.1115615225079.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <538547385.1113513322861.JavaMail.jira@ajax.apache.org>
	 <1216407538.1115615225079.JavaMail.jira@ajax.apache.org>

I got the html copy of this change from Jeff and the change looks
good. Thanks for taking care of this, Jeff.

On 5/8/05, Jeff Levitt (JIRA) <derby-dev@db.apache.org> wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-227?page=3Dall ]
>=20
> Jeff Levitt updated DERBY-227:
> ------------------------------
>=20
>    Attachment: derby227.diff
>=20
> The attached derby227.diff patch removes the Implementation notes cell fr=
om the prepareCall row of this table.  It then extendes the Implementation =
notes cell shared by the createstatement and preparestatement cells, so in =
effect, they all read the same.  This is in the rrefjdbc80004.dita file.
>=20
> > Reference manual has incorrect information for supported resultset type=
s for prepareCall JDBC api
> > -----------------------------------------------------------------------=
--------------------------
> >
> >          Key: DERBY-227
> >          URL: http://issues.apache.org/jira/browse/DERBY-227
> >      Project: Derby
> >         Type: Bug
> >   Components: Documentation
> >     Versions: 10.1.0.0
> >     Reporter: Mamta A. Satoor
> >  Attachments: derby227.diff
> >
> > Reference manual at http://incubator.apache.org/derby/manuals/reference=
/sqlj210.html#HDRSII-JDBC-80004 says that ResultSet.Type_FORWARD_ONLY is th=
e only resultSet type supported for prepareCall. That is not correct. prepa=
reCall supports ResultSet.TYPE_FORWARD_ONLY and ResultSet.TYPE_SCROLL_INSEN=
SITIVE (similar to createStatement and prepareStatement). In short, the col=
umn 3 of the table should have same information for createStatement, prepar=
eStatement and prepareCall.
>=20
> --
> 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
>=20
>