You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jeff Levitt (JIRA)" <de...@db.apache.org> on 2005/05/09 07:07:06 UTC

[jira] Updated: (DERBY-227) Reference manual has incorrect information for supported resultset types for prepareCall JDBC api

     [ http://issues.apache.org/jira/browse/DERBY-227?page=all ]

Jeff Levitt updated DERBY-227:
------------------------------

    Attachment: derby227.diff

The attached derby227.diff patch removes the Implementation notes cell from 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.


> Reference manual has incorrect information for supported resultset types 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 the only resultSet type supported for prepareCall. That is not correct. prepareCall supports ResultSet.TYPE_FORWARD_ONLY and ResultSet.TYPE_SCROLL_INSENSITIVE (similar to createStatement and prepareStatement). In short, the column 3 of the table should have same information for createStatement, prepareStatement and prepareCall.

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