[
https://issues.apache.org/jira/browse/DERBY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-3169:
-----------------------------
Attachment: DERBY-3169-5.zip
DERBY-3169-5.diff
Thanks, Jørgen, for the comment. Here are new diff and zip files with the
one-word change (DERBY-3169-5.diff and DERBY-3169-5.zip). I wonder if it would
make sense to commit these now, without resolving the issue, just so any
subsequent changes could be incremental? (I haven't yet learned how to commit,
so someone else would need to do this.)
I can see that implementing the SYSCS_UTIL.SYSCS_PREPARE_REPLICATION procedure
would require only a new file in the Reference Manual and some changes to the
"Starting and running replication" topic of the Admin Guide.
There was also something in the comments to DERBY-3552 about a possible need
for documentation concerning jar files, but I don't quite understand this issue
yet so I'm not sure what would be involved.
> Add documentation for replication
> ---------------------------------
>
> Key: DERBY-3169
> URL: https://issues.apache.org/jira/browse/DERBY-3169
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.4.0.0
> Reporter: Jørgen Løland
> Assignee: Kim Haase
> Attachments: DERBY-3169-2.diff, DERBY-3169-2.stat, DERBY-3169-2.zip,
> DERBY-3169-3.diff, DERBY-3169-3.stat, DERBY-3169-3.zip, DERBY-3169-4.diff,
> DERBY-3169-4.zip, DERBY-3169-5.diff, DERBY-3169-5.zip, DERBY-3169.diff,
> DERBY-3169.stat, DERBY-3169.zip
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
