Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 47244 invoked from network); 19 Mar 2007 16:25:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Mar 2007 16:25:59 -0000 Received: (qmail 1537 invoked by uid 500); 19 Mar 2007 16:26:02 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 1226 invoked by uid 500); 19 Mar 2007 16:26:01 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 1205 invoked by uid 99); 19 Mar 2007 16:26:01 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2007 09:26:01 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2007 09:25:52 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 95AC2714070 for ; Mon, 19 Mar 2007 09:25:32 -0700 (PDT) Message-ID: <2184815.1174321532608.JavaMail.jira@brutus> Date: Mon, 19 Mar 2007 09:25:32 -0700 (PDT) From: "Laura Stewart (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-1520) Document new SYSCS_DIAG tables In-Reply-To: <18871481.1153155254360.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482140 ] Laura Stewart commented on DERBY-1520: -------------------------------------- ... Hmmm, let me check into this. I thought that I had my system set up to automatically resolve the line breaks... And this is weird, because I don't think that you noticed this with other patches that I have committed. But maybe I didn't change the ditamap with those patche. -- Laura Stewart > 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.