[ http://issues.apache.org/jira/browse/DERBY-1930?page=comments#action_12440016 ] Dag H. Wanvik commented on DERBY-1930: --------------------------------------
Some updates to this page for SUR: > java.sql.Connection > Clarification for createStatement(), prepareStatement() and > prepareCall() CONCUR_UPDATABLE concurrency is supported for FORWARD > ONLY ResultSet types only. The last two lines should read CONCUR_UPDATABLE concurrency is supported for TYPE_FORWARD_ONLY and TYPE_SCROLL_INSENSITIVE ResultSet types only." > Clarification for deleteRow() > After deleteRow, ResultSet will be positioned right before the next > row for FORWARD ONLY updatable ResultSets. The last sentence should read: "After deleteRow, ResultSet will be positioned right before the next row for TYPE_FORWARD_ONLY and TYPE_SCROLL_INSENSITIVE updatable ResultSets." > Clarification for updateRow() > After updateRow, ResultSet will be positioned right before the next > row for FORWARD ONLY updatable ResultSets. The last sentence should read: "After updateRow, ResultSet will be positioned right before the next row for TYPE_FORWARD_ONLY updatable ResultSets. The ResultSet remain on the current row for TYPE_SCROLL_INSENSITIVE updatable ResultSets." > Move JDBC implementation notes into the published javadoc > --------------------------------------------------------- > > Key: DERBY-1930 > URL: http://issues.apache.org/jira/browse/DERBY-1930 > Project: Derby > Issue Type: Improvement > Components: Documentation, JDBC > Reporter: Daniel John Debrunner > Assigned To: Daniel John Debrunner > Priority: Minor > Fix For: 10.3.0.0 > > Attachments: package-summary.html > > > The information in Derby's JDBC implementation notes needs to be in the > documentation. > http://db.apache.org/derby/papers/JDBCImplementation.html > At least one approach is to add it to the published Javadoc in the > package.html for org.apache.derby.jdbc. > This will make it easier for people to update and ensures that users of Derby > have the information with a release. -- 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
