db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1520) Document new SYSCS_DIAG tables
Date Mon, 19 Mar 2007 16:09:32 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482138

A B commented on DERBY-1520:

Laura > Unfortnately it's not that simple. Since the patch derby1520_3.diff was commited,

If the fact that the patch has been committed is really a problem, couldn't you (as a committer)
simply revert the change, create a fresh patch that has whatever the correct changes are,
and then re-commit the corrected patch?

To "revert" or "back out" a committed patch you just run the "merge" command with the revision
number(s) in reverse, then svn add/delete files just like for a normal patch. Ex.

   svn merge -r 518684:518683 https://svn.apache.org/repos/asf/db/derby/docs/trunk

should revert the patch for this issue in your local client; then if you do an "svn commit"
that should effectively back-out the changes...

Maybe usfeul, maybe not.  Just thought I'd mention it.  Note that I don't actually have a
doc trunk on my machine so I can't guarantee that the above command will work; but I ran a
similar command on the my local trunk as a test and it seems to have done the trick.

PS I do still plan to review the changes for this issue; the latest version is looking a lot
better, but there are still some clarifications that I think would be good.  Hoping to get
to that in the next couple of days...

> Document new SYSCS_DIAG tables
> ------------------------------
>                 Key: DERBY-1520
>                 URL: https://issues.apache.org/jira/browse/DERBY-1520
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>    Affects Versions:
>            Reporter: Stan Bradbury
>         Assigned To: Laura Stewart
>         Attachments: derby1520_1.diff, derby1520_2.diff, derby1520_3.diff, derby1520_4.diff,
refderby.ditamap, rrefsyscsdiagtables.html, rrefsyscsdiagtables.html
> See comments for DERBY-571 for initial documentation discussion.  The new tables (mapped
to the old Diagnostic VTIs) are:
> The old style syntax will remain in place for 10.2, but become deprecated.
> The tables to be implemented in this change are:
> SYSCS_DIAG.LOCK_TABLE replaces org.apache.derby.diag.LockTable
> SYSCS_DIAG.STATEMENT_CACHE replaces org.apache.derby.diag.StatementCache
> SYSCS_DIAG.TRANSACTION_TABLE replaces org.apache.derby.diag.TransactionTable
> SYSCS_DIAG.ERROR_MESSAGES replaces org.apache.derby.diag.ErrorMessages 
> The information about the tables can be found in the javadoc for the class listed above.
> That can be found at:
> http://db.apache.org/derby/javadoc/engine/
> click on the org.apache.derby.diag link in the Packages table, then select each class,
e.g. LockTable to see the info.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message