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

Kim Haase commented on DERBY-1520:
----------------------------------

Right, the ditamap changes relatively rarely, and I don't think it is usually 
attached to an issue -- it is considered a source file, so what we usually see 
is the diffs file and the HTML files. 

I think the line ending problem is fixed when you use the command "svn propset 
svn:eol-style native <filename>" and also when you do a commit, because the svn 
properties file has the line

   *.ditamap = svn:eol-style=native

So that would explain why the problem doesn't usually show up with checked-in 
files.


> 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: 10.2.1.6
>            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.

Reply via email to