db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Levitt (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-332) Documentation changes for updatable ResultSets
Date Wed, 08 Jun 2005 06:31:47 GMT
    [ http://issues.apache.org/jira/browse/DERBY-332?page=comments#action_12313013 ] 

Jeff Levitt commented on DERBY-332:

But the changes are already committed?  I just did a clean checkout of the DITA source files
and found the files to already include the changes in this patch.  And the nightly builds
of the output also show the correct changes.  See the following file as an example:


Perhaps someone committed it and didn't record it in JIRA?  That would definitely explain
why you can't commit it again?

> Documentation changes for updatable ResultSets
> ----------------------------------------------
>          Key: DERBY-332
>          URL: http://issues.apache.org/jira/browse/DERBY-332
>      Project: Derby
>         Type: Improvement
>   Components: Documentation
>     Versions:
>     Reporter: Andrew McIntyre
>  Attachments: resultsets_changes.diff
> Derby's documentation needs to be updated with information on updatable ResultSets. A
patch was already submitted and reviewed, but not committed in the thread "[patch][doc] updatable
ResultSets" which can be found here:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200504.mbox/%3c20050415205241.42950.qmail@web90205.mail.scd.yahoo.com%3e
> I am opening this JIRA and attaching the patch here so that it is not forgotten.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message