[jira] Updated: (DERBY-1057) documentation to address Grant/Revoke (Derby-464)
[ http://issues.apache.org/jira/browse/DERBY-1057?page=all ] Eric Radzinski updated DERBY-1057: -- Attachment: derby1057_ref.diff derby1057_ref_html.zip derby1057_ref.diff addresses changes to the Reference Guide that relate to Grant/Revoke. HTML files are included for review. Note that this patch does not address all of the doc changes that relate to Grant/Revoke. Additional changes to the Developer's Guide (specifically to the "User authorization" information) will be provided in a separate patch. > documentation to address Grant/Revoke (Derby-464) > - > > Key: DERBY-1057 > URL: http://issues.apache.org/jira/browse/DERBY-1057 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.0.2.0 > Reporter: Eric Radzinski > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: derby1057_ref.diff, derby1057_ref_html.zip > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DERBY-1057) documentation to address Grant/Revoke (Derby-464)
documentation to address Grant/Revoke (Derby-464) - Key: DERBY-1057 URL: http://issues.apache.org/jira/browse/DERBY-1057 Project: Derby Type: Sub-task Components: Documentation Versions: 10.0.2.0 Reporter: Eric Radzinski Assigned to: Eric Radzinski Fix For: 10.2.0.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-916) documentation to address Derby-239: online backup
[ http://issues.apache.org/jira/browse/DERBY-916?page=comments#action_12367744 ] Eric Radzinski commented on DERBY-916: -- Can somebody take a look at the doc patch for this issue? > documentation to address Derby-239: online backup > - > > Key: DERBY-916 > URL: http://issues.apache.org/jira/browse/DERBY-916 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.0.2.0 > Reporter: Eric Radzinski > Assignee: Eric Radzinski > Attachments: derby916-1.diff, derby916_html_files.zip > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-608) Documentation will require changes once dynamic parameters are supported for unary minus and unary plus.
[ http://issues.apache.org/jira/browse/DERBY-608?page=all ] Eric Radzinski updated DERBY-608: - Attachment: rrefsqlj1083019.html derby608.diff derby608.diff implements Mamta's comments. The HTML file is included for review. > Documentation will require changes once dynamic parameters are supported for > unary minus and unary plus. > > > Key: DERBY-608 > URL: http://issues.apache.org/jira/browse/DERBY-608 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Fix For: 10.2.0.0 > Attachments: derby608.diff, rrefsqlj1083019.html > > Once Derby-582 is resolved, the documentation for unary -/+ should be updated > to reflect support for dynamic parameters for unary +/-. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-608) Documentation will require changes once dynamic parameters are supported for unary minus and unary plus.
[ http://issues.apache.org/jira/browse/DERBY-608?page=comments#action_12366546 ] Eric Radzinski commented on DERBY-608: -- Can somebody confirm that the only doc change related to this issue is removing the following note from the Reference Guide. It's in the topic titled "Where dynamic parameters are allowed" 13. A dynamic parameter is not allowed as the operand of the unary operators - or +. Are there any other doc hits? > Documentation will require changes once dynamic parameters are supported for > unary minus and unary plus. > > > Key: DERBY-608 > URL: http://issues.apache.org/jira/browse/DERBY-608 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Fix For: 10.2.0.0 > > Once Derby-582 is resolved, the documentation for unary -/+ should be updated > to reflect support for dynamic parameters for unary +/-. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: derby855-5.diff ctundepthoptover.html ctunoptimzoverride.html derby855-5.diff addresses the line break error in the joinOrder example. HTML files are included for review. > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > derby855-2.diff, derby855-3.diff, derby855-4.diff, derby855-5.diff, > derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: (was: ctunoptimzoverride.html) > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: derby855-2.diff, derby855-3.diff, derby855-4.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: (was: ctundepthoptover.html) > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: derby855-2.diff, derby855-3.diff, derby855-4.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-916) documentation to address Derby-239: online backup
[ http://issues.apache.org/jira/browse/DERBY-916?page=all ] Eric Radzinski updated DERBY-916: - Attachment: derby916-1.diff derby916_html_files.zip This patch addresses the changes to online backups. It adds the following four new topics to the Reference Guide: SYSCS_UTIL.SYSCS_ONLINE_BACKUP_DATABASE_NOWAIT SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE_NOWAIT SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE SYSCS_UTIL.SYSCS_DISABLE_LOG_ARCHIVE_MODE And affects five files in the Server and Admin Guide. The HTML files are included for review. > documentation to address Derby-239: online backup > - > > Key: DERBY-916 > URL: http://issues.apache.org/jira/browse/DERBY-916 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.0.2.0 > Reporter: Eric Radzinski > Assignee: Eric Radzinski > Attachments: derby916-1.diff, derby916_html_files.zip > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: derby855-4.diff ctundepthoptover.html ctunoptimzoverride.html sorry about that. The editor that I was using was inserting an endash instead of two single dashes. derby855-4.diff addresses the problem. New html files included for review. > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > derby855-2.diff, derby855-3.diff, derby855-4.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: (was: ctunoptimzoverride.html) > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: derby855-2.diff, derby855-3.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: (was: ctundepthoptover.html) > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: derby855-2.diff, derby855-3.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: derby855-3.diff ctundepthoptover.html ctunoptimzoverride.html derby855-3.diff updates the description of the joinStrategy property and updates the example for the joinStrategy property. The HTML files are included for review. > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > derby855-2.diff, derby855-3.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: (was: ctunoptimzoverride.html) > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: derby855-2.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: (was: ctunoptimzoverride.html) > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: derby855-2.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: (was: ctundepthoptover.html) > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: derby855-2.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: (was: tuning_guide.zip) > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > ctunoptimzoverride.html, derby855-2.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: (was: derby855_html_files.zip) > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > ctunoptimzoverride.html, derby855-2.diff, derby855.diff > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12365764 ] Eric Radzinski commented on DERBY-855: -- sorry...I meant only the second-to-last paragraph is new. > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > ctunoptimzoverride.html, derby855-2.diff, derby855.diff, > derby855_html_files.zip, tuning_guide.zip > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12365762 ] Eric Radzinski commented on DERBY-855: -- How's this (only the second-to-last sentence is new): joinStrategy Use the joinStrategy property to override the optimizer's choice of join strategy. The two types of join strategy are called nested loop and hash. In a nested loop join strategy, for each qualifying row in the outer table, Derby uses the appropriate access path (index or table scan) to find the matching rows in the inner table. In a hash join strategy, Derby constructs a hash table that represents the inner table. For each qualifying row in the outer table, Derby does a quick lookup on the hash table to find the matching rows in the inner table. Derby needs to scan the inner table or index only once to create the hash table. The -DERBY-PROPERTIES parameter must immediately follow the inner table. Typically, you will use the joinStrategy property only in conjunction with the joinOrder property. Specifying a join strategy without knowing the join order can yield less-than-optimal results. Valid values include HASH and NESTEDLOOP. The joinStrategy property can be used only within a TableExpression. > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > ctunoptimzoverride.html, derby855-2.diff, derby855.diff, > derby855_html_files.zip, tuning_guide.zip > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-571) Virtual Table Mapping for no argument Diagnostic tables
[
http://issues.apache.org/jira/browse/DERBY-571?page=comments#action_12365663 ]
Eric Radzinski commented on DERBY-571:
--
Does this issue require some documentation (e.g., do the four new system tables
need to be doc'd in the Ref Guide?)
> Virtual Table Mapping for no argument Diagnostic tables
> ---
>
> Key: DERBY-571
> URL: http://issues.apache.org/jira/browse/DERBY-571
> Project: Derby
> Type: Improvement
> Components: SQL
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.2.0.0
>
> Currently four no-argument diagnostic tables exist that provide information
> about the running state of Derby, or its error messages.
> These tables are invoked using an awkward, non-standard syntax. As an example:
> SELECT * FROM NEW org.apache.derby.diag.LockTable() as LOCK_TABLE
> The improvement will provide an internal mapping from a regular table name in
> the SYSCS_DIAG schema
> to the runtime virtual table code. Thus the above example would be replaced
> by:
> SELECT * FROM SYSCS_DIAG.LOCK_TABLE
> These diagnostic table expressions are regular table expressions (as is the
> NEW VTI construct) and
> can be used wherever a normal table can.
> Any DDL, INSERT/UPDATE/DELETE, compression procedure etc. that references a
> diagnostic table
> will result in an exception.
> 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_CACHEreplaces org.apache.derby.diag.StatementCache
> SYSCS_DIAG.TRANSACTION_TABLEreplaces
> org.apache.derby.diag.TransactionTable
> SYSCS_DIAG.ERROR_MESSAGESreplaces org.apache.derby.diag.ErrorMessages
> Adding such a table will be table driven, thus easy for others to provide
> additional diagnostics.
> Information about these diagnostic tables will not appear in the system
> catalogs or JDBC DatabaseMetaData.
> The ResultSetMetaData for the any query involving a diagnostic table will be
> valid.
> This is a first step in a progression towards supporing a fully
> application/user defined virtual table.
> These steps are not part of this jira issue, but added for information
> purposes.
> - second step - supporting diagnostic tables with parameters, e.g.
> SELECT * FROM SYSCS_DIAG.SPACE_TABLE('sales', 'orders');
> - third step - providing a create virtual table statement (most databases
> support
>some form of virtual table, or wrappers). The DDL would be non-standard
> but the
>data access would be standard. [need to check table functions in part 13
> of SQL standard]
>E.g. syntax yet to be defined, but to give the general idea
> CREATE VIRTUAL TABLE (TICKER VARCHAR(10), START TIMESTAMP, END
> TIMESTAMP)
>LANGUAGE JAVA
>PARAMETER STYLE JAVA
>EXTERNAL NAME 'com.acme.stocks.historyFromYahooFinance';
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: derby855-2.diff tuning_guide.zip Mamta, the newest patch (derby855-2.diff) addresses your comments about the errant semicolons and about the line breaks in the example syntax. All of the related linking is controlled by the ditamap, so I don't need to explicitly add those links. We get them for free. I've attached the HTML version of the entire Tuning Guide so that you can see all of the links that were generated. Unzip the tuning_guide.zip file, open the toc.html file, and then take a look at the new topics and the topics that relate to them. > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > ctunoptimzoverride.html, derby855-2.diff, derby855.diff, > derby855_html_files.zip, tuning_guide.zip > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: derby855.diff derby855_html_files.zip The attached patch addresses the optimizer overrides that were implemented with DERBY-573. The HTML files are included for review. I also included the HTML TOC file so that you can see where the new files were incorporated into the ditamap. "Optimizer overrides" was added as the last subtopic under "Working with RunTimeStatistics" -> "Analyzing the information" "Overriding the default optimizer behavior" was added as the last subtopic under "DML statements and performance" > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > ctunoptimzoverride.html, derby855.diff, derby855_html_files.zip > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-761) The reserved words list in the reference manual doesn't look uptodate
[ http://issues.apache.org/jira/browse/DERBY-761?page=all ] Eric Radzinski updated DERBY-761: - Attachment: (was: rrefkeywords29722.html) > The reserved words list in the reference manual doesn't look uptodate > - > > Key: DERBY-761 > URL: http://issues.apache.org/jira/browse/DERBY-761 > Project: Derby > Type: Bug > Components: Documentation > Reporter: Mamta A. Satoor > Attachments: derby761-2.diff, derby761-3.diff, derby761.diff, > rrefkeywords29722.html > > I looked at the 10.1 reference manual's reserved word list and noticed > keywords like BINARY, COALESCE missing from the list. Haven't checked the > list thoroughly to see what else might be missing but it would be good to fix > this for 10.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-761) The reserved words list in the reference manual doesn't look uptodate
[ http://issues.apache.org/jira/browse/DERBY-761?page=all ] Eric Radzinski updated DERBY-761: - Attachment: derby761-3.diff rrefkeywords29722.html latest patch changes _DEFAULT to DEFAULT. > The reserved words list in the reference manual doesn't look uptodate > - > > Key: DERBY-761 > URL: http://issues.apache.org/jira/browse/DERBY-761 > Project: Derby > Type: Bug > Components: Documentation > Reporter: Mamta A. Satoor > Attachments: derby761-2.diff, derby761-3.diff, derby761.diff, > rrefkeywords29722.html > > I looked at the 10.1 reference manual's reserved word list and noticed > keywords like BINARY, COALESCE missing from the list. Haven't checked the > list thoroughly to see what else might be missing but it would be good to fix > this for 10.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-570) wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Eric Radzinski updated DERBY-570: - Attachment: rrefsqlj30118.html derby570-3.diff derby570-3.diff removes the compile time type section from the topic. Latest HTML file is included for review. > wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA > > > Key: DERBY-570 > URL: http://issues.apache.org/jira/browse/DERBY-570 > Project: Derby > Type: Bug > Components: Documentation > Versions: 10.1.1.0 > Reporter: Rick Hillegas > Attachments: derby570-2.diff, derby570-3.diff, derby570.diff, > rrefsqlj30118.html > > The Datatypes section of the Reference Manual says that LONG VARCHAR FOR BIT > DATA is identical to VARCHAR FOR BIT DATA but does not give a jdbc type, > implying that LONG VARCHAR FOR BIT DATA has the same jdbc type as VARCHAR FOR > BIT DATA, i.e., VARBINARY. This section should say that LONG VARCHAR FOR BIT > DATA has the following jdbc type: LONGVARBINARY. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-570) wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Eric Radzinski updated DERBY-570: - Attachment: (was: rrefsqlj30118.html) > wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA > > > Key: DERBY-570 > URL: http://issues.apache.org/jira/browse/DERBY-570 > Project: Derby > Type: Bug > Components: Documentation > Versions: 10.1.1.0 > Reporter: Rick Hillegas > Attachments: derby570-2.diff, derby570.diff > > The Datatypes section of the Reference Manual says that LONG VARCHAR FOR BIT > DATA is identical to VARCHAR FOR BIT DATA but does not give a jdbc type, > implying that LONG VARCHAR FOR BIT DATA has the same jdbc type as VARCHAR FOR > BIT DATA, i.e., VARBINARY. This section should say that LONG VARCHAR FOR BIT > DATA has the following jdbc type: LONGVARBINARY. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-761) The reserved words list in the reference manual doesn't look uptodate
[ http://issues.apache.org/jira/browse/DERBY-761?page=all ] Eric Radzinski updated DERBY-761: - Attachment: derby761-2.diff rrefkeywords29722.html This patch and HTML file are based on Sateesh's list. Note that several of the keywords that Mamta originally suggested including are not present. These include: BINARY, CHARACTER_LENGTH, D, MODULE, T, TS, VALUE, and VARBINARY. And this list does include INOUT and NVARCHAR, which Mamta suggested deleting. > The reserved words list in the reference manual doesn't look uptodate > - > > Key: DERBY-761 > URL: http://issues.apache.org/jira/browse/DERBY-761 > Project: Derby > Type: Bug > Components: Documentation > Reporter: Mamta A. Satoor > Attachments: derby761-2.diff, derby761.diff, rrefkeywords29722.html > > I looked at the 10.1 reference manual's reserved word list and noticed > keywords like BINARY, COALESCE missing from the list. Haven't checked the > list thoroughly to see what else might be missing but it would be good to fix > this for 10.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-761) The reserved words list in the reference manual doesn't look uptodate
[ http://issues.apache.org/jira/browse/DERBY-761?page=all ] Eric Radzinski updated DERBY-761: - Attachment: (was: rrefkeywords29722.html) > The reserved words list in the reference manual doesn't look uptodate > - > > Key: DERBY-761 > URL: http://issues.apache.org/jira/browse/DERBY-761 > Project: Derby > Type: Bug > Components: Documentation > Reporter: Mamta A. Satoor > Attachments: derby761.diff > > I looked at the 10.1 reference manual's reserved word list and noticed > keywords like BINARY, COALESCE missing from the list. Haven't checked the > list thoroughly to see what else might be missing but it would be good to fix > this for 10.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-570) wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Eric Radzinski updated DERBY-570: - Attachment: derby570-2.diff rrefsqlj30118.html The newest patch and HTML file address Dan's suggestion. I've reformatted the topic to match the other data type topics. Also, the suggested compile time to use was "byte [ ]" All the other data type topics used the fully-qualified name though, so I used java.lang.Byte. Let me know if that's not correct. > wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA > > > Key: DERBY-570 > URL: http://issues.apache.org/jira/browse/DERBY-570 > Project: Derby > Type: Bug > Components: Documentation > Versions: 10.1.1.0 > Reporter: Rick Hillegas > Attachments: derby570-2.diff, derby570.diff, rrefsqlj30118.html > > The Datatypes section of the Reference Manual says that LONG VARCHAR FOR BIT > DATA is identical to VARCHAR FOR BIT DATA but does not give a jdbc type, > implying that LONG VARCHAR FOR BIT DATA has the same jdbc type as VARCHAR FOR > BIT DATA, i.e., VARBINARY. This section should say that LONG VARCHAR FOR BIT > DATA has the following jdbc type: LONGVARBINARY. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-570) wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Eric Radzinski updated DERBY-570: - Attachment: (was: rrefsqlj30118.html) > wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA > > > Key: DERBY-570 > URL: http://issues.apache.org/jira/browse/DERBY-570 > Project: Derby > Type: Bug > Components: Documentation > Versions: 10.1.1.0 > Reporter: Rick Hillegas > Attachments: derby570.diff > > The Datatypes section of the Reference Manual says that LONG VARCHAR FOR BIT > DATA is identical to VARCHAR FOR BIT DATA but does not give a jdbc type, > implying that LONG VARCHAR FOR BIT DATA has the same jdbc type as VARCHAR FOR > BIT DATA, i.e., VARBINARY. This section should say that LONG VARCHAR FOR BIT > DATA has the following jdbc type: LONGVARBINARY. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-761) The reserved words list in the reference manual doesn't look uptodate
[ http://issues.apache.org/jira/browse/DERBY-761?page=all ] Eric Radzinski updated DERBY-761: - Attachment: derby761.diff rrefkeywords29722.html attached patch addresses derby-761. HTML file is included for review. > The reserved words list in the reference manual doesn't look uptodate > - > > Key: DERBY-761 > URL: http://issues.apache.org/jira/browse/DERBY-761 > Project: Derby > Type: Bug > Components: Documentation > Reporter: Mamta A. Satoor > Attachments: derby761.diff, rrefkeywords29722.html > > I looked at the 10.1 reference manual's reserved word list and noticed > keywords like BINARY, COALESCE missing from the list. Haven't checked the > list thoroughly to see what else might be missing but it would be good to fix > this for 10.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-570) wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Eric Radzinski updated DERBY-570: - Attachment: derby570.diff rrefsqlj30118.html The attached patch adds the requested line ot the LONG VARCHAR FOR BIT DATA topic. HTML file is included for review. > wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA > > > Key: DERBY-570 > URL: http://issues.apache.org/jira/browse/DERBY-570 > Project: Derby > Type: Bug > Components: Documentation > Versions: 10.1.1.0 > Reporter: Rick Hillegas > Attachments: derby570.diff, rrefsqlj30118.html > > The Datatypes section of the Reference Manual says that LONG VARCHAR FOR BIT > DATA is identical to VARCHAR FOR BIT DATA but does not give a jdbc type, > implying that LONG VARCHAR FOR BIT DATA has the same jdbc type as VARCHAR FOR > BIT DATA, i.e., VARBINARY. This section should say that LONG VARCHAR FOR BIT > DATA has the following jdbc type: LONGVARBINARY. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-761) The reserved words list in the reference manual doesn't look uptodate
[ http://issues.apache.org/jira/browse/DERBY-761?page=comments#action_12365094 ] Eric Radzinski commented on DERBY-761: -- If somebody can provide a complete list of reserved words, I'll update the reference guide. > The reserved words list in the reference manual doesn't look uptodate > - > > Key: DERBY-761 > URL: http://issues.apache.org/jira/browse/DERBY-761 > Project: Derby > Type: Bug > Components: Documentation > Reporter: Mamta A. Satoor > > I looked at the 10.1 reference manual's reserved word list and noticed > keywords like BINARY, COALESCE missing from the list. Haven't checked the > list thoroughly to see what else might be missing but it would be good to fix > this for 10.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-916) documentation to address Derby-239: online backup
[ http://issues.apache.org/jira/browse/DERBY-916?page=comments#action_12365020 ] Eric Radzinski commented on DERBY-916: -- Can somebody confirm that this is what is required to document Derby-239: Reference Guide: Add the following two new stored procedures: --SYSC_UTIL.SYSCS_ONLINE_BACKUP_DATABASE_NOWAIT and --SYSC_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE_NOWAIT Also, it doesn't look like there are any changes to the SYSCS_UTIL.SYSCS_BACKUP_DATABASE topic. Is that correct? Server and Admin Guide: --Remove references to update operations not being possible during a backup (there are a lot of these) --Add topic about performing an online backup in which unlogged operations immediately return an error. Anything else? > documentation to address Derby-239: online backup > - > > Key: DERBY-916 > URL: http://issues.apache.org/jira/browse/DERBY-916 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.0.2.0 > Reporter: Eric Radzinski > Assignee: Eric Radzinski > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DERBY-916) documentation to address Derby-239: online backup
documentation to address Derby-239: online backup - Key: DERBY-916 URL: http://issues.apache.org/jira/browse/DERBY-916 Project: Derby Type: Sub-task Components: Documentation Versions: 10.0.2.0 Reporter: Eric Radzinski Assigned to: Eric Radzinski -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-701) Java 2 security policy file examples don't work -- are missing a needed line
[ http://issues.apache.org/jira/browse/DERBY-701?page=all ]
Eric Radzinski updated DERBY-701:
-
Attachment: derby701-2.diff
derby701_html_files-2.zip
Attached patch addresses changes to both the Server Gd. and to the Dev. Gd.
HTML files are included for review.
> Java 2 security policy file examples don't work -- are missing a needed line
>
>
> Key: DERBY-701
> URL: http://issues.apache.org/jira/browse/DERBY-701
> Project: Derby
> Type: Bug
> Components: Documentation
> Versions: 10.1.1.1
> Reporter: Jean T. Anderson
> Priority: Minor
> Attachments: derby701-2.diff, derby701.diff, derby701_html_files-2.zip,
> derby701_html_files.zip
>
> These security policy file examples don't work as is:
>http://db.apache.org/derby/docs/dev/devguide/rdevcsecure871406.html
>http://db.apache.org/derby/docs/dev/devguide/rdevcsecure871422.html
>http://db.apache.org/derby/docs/dev/devguide/rdevcsecure871439.html
> Each example needs this additional line:
>permission java.io.FilePermission "${derby.system.home}","read";
> The email thread is here:
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200511.mbox/[EMAIL
> PROTECTED]
> To show one of the examples, here is the current text for Example 1:
> grant codeBase "file://f:/derby/lib/derby.jar" {
> permission java.lang.RuntimePermission "createClassLoader";
> permission java.util.PropertyPermission "derby.*", "read";
> permission java.io.FilePermission "${derby.system.home}${/}-",
> "read,write,delete";
> };
> It needs to be this instead:
> grant codeBase "file://f:/derby/lib/derby.jar" {
>permission java.lang.RuntimePermission "createClassLoader";
>permission java.util.PropertyPermission "derby.*", "read";
>permission java.io.FilePermission "${derby.system.home}","read";
>permission java.io.FilePermission
> "${derby.system.home}${/}-","read,write,delete";
> };
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[
http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12364849 ]
Eric Radzinski commented on DERBY-855:
--
There's three open issues on derby-855. I've summarized them here:
--- Does this text adequately address your concern about the description of the
constraint property:
constraint
To force the use of the index that enforces a primary key, a foreign key, or
unique constraint, use the constraint property and specify the
unqualified name of the constraint. The constraint property can be used only
within a TableExpression, and it
can be specified only on base tables; it cannot be specified on views or
derived tables.
--- I haven't seen a response about my proposal to modify the syntax to include
the properties in the syntax. Here's what I proposed on 1/27:
The syntax for FROM clause properties is:
FROM [ -- DERBY-PROPERTIES joinOrder = FIXED | UNFIXED ]
TableExpression [,TableExpression]*
The syntax for table optimizer override properties, which must be included at
the end of a TableExpression, is:
{TableName | ViewName }
[ [ AS ] CorrelationName
[ (SimpleColumnName [ , SimpleColumnName]* ) ] ]
[ -- DERBY-PROPERTIES constraint= |
index= | joinStrategy = NESTEDLOOP | HASH ]
--- Regarding the comment about runstats output, is there a doc to-do in this
comment? or does this apply only to the output when a foreign key is
specified? If there is a doc to-do, can you provide me some details about what
it should include?
> Document optimizer overrides which were introduced in 10.2
> --
>
> Key: DERBY-855
> URL: http://issues.apache.org/jira/browse/DERBY-855
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Assignee: Eric Radzinski
> Fix For: 10.2.0.0
> Attachments: ctundepthoptover.html, ctunoptimzoverride.html,
> ctunoptimzoverride.html
>
> Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric
> Radzinski is working on the documentation part of the feature. This issue is
> to keep track of documentation changes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: ctunoptimzoverride.html I think the most recent ctunoptimzoverride.htm addresses your first two issues (adding a pointer to the runtimestats topic and removing the space between nested and loop). The third issue is a simple change that I'll make as soon as I add these two new topics to the ditamap for the tuning guide. Please let me know if you think these topics are ready to commit. > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html, > ctunoptimzoverride.html > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[
http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12364265 ]
Eric Radzinski commented on DERBY-855:
--
Regarding your first point, do you suggest to remove the description about the
default optimizer behaviour, and just include something like this:
constraint
Use the constraint property to override the index that the optimizer selects
and force the use of a particular index or force a table scan.
To force the use of the index that enforces a primary key or unique constraint,
use the constraint property and specify the
unqualified name of the constraint.
And regarding your second point, would updating the syntax at the top of the
topic resolve this issue:
The syntax for FROM clause properties is:
FROM [ -- DERBY-PROPERTIES joinOrder = FIXED | UNFIXED ]
TableExpression [,TableExpression]*
The syntax for table optimizer override properties, which must be included at
the end of a TableExpression, is:
{TableName | ViewName }
[ [ AS ] CorrelationName
[ (SimpleColumnName [ , SimpleColumnName]* ) ] ]
[ -- DERBY-PROPERTIES constraint= |
index= | joinStrategy = NESTED LOOP | HASH ]
> Document optimizer overrides which were introduced in 10.2
> --
>
> Key: DERBY-855
> URL: http://issues.apache.org/jira/browse/DERBY-855
> Project: Derby
> Type: Sub-task
> Components: Documentation
> Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Assignee: Eric Radzinski
> Fix For: 10.2.0.0
> Attachments: ctundepthoptover.html, ctunoptimzoverride.html
>
> Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric
> Radzinski is working on the documentation part of the feature. This issue is
> to keep track of documentation changes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski updated DERBY-855: - Attachment: ctunoptimzoverride.html ctundepthoptover.html I think I've addressed all of the open issues. ctunoptimzoverride.html is a new topic that's titled "Overriding the default optimizer behaviour." It'll go in the "Performance and optimization" section of the Tuning Guide. ctundepthoptover is a new topic that's titled "Optimizer overrides." It'll go in the "Working with RunTimeStatistics" section of the Tuning Guide. I'll add the appropriate related links after everybody's satisfied with the content of these two topics. > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > Attachments: ctundepthoptover.html, ctunoptimzoverride.html > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-869) documentation to address Derby-783
[ http://issues.apache.org/jira/browse/DERBY-869?page=all ] Eric Radzinski updated DERBY-869: - Attachment: derby869.diff rrefsqlj81859.html All set. I've incorporated your latest comments. Patch and HTML file are included. > documentation to address Derby-783 > -- > > Key: DERBY-869 > URL: http://issues.apache.org/jira/browse/DERBY-869 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.0.2.0 > Reporter: Eric Radzinski > Assignee: Eric Radzinski > Attachments: derby869.diff, derby869.diff, rrefsqlj81859.html, > rrefsqlj81859.html > > document changes to ALTER TABLE syntax to address Derby-783 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12364115 ] Eric Radzinski commented on DERBY-855: -- I have a few outstanding questions about documenting this issue: --I need some help extracting relevant examples from the source that you provided, which is located in: db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master/optimizerOverrides.out. Which specific ones would be best to use? --Satheesh mentioned that we need to let the users know that they can see their optimizer overrides in RUNSTAT output. I'm assuming that this update would go in the tuning guide as a separate topic in the "Working with RunTimeStatistics" section. Can you confirm this? --I need to mention whether the four properties belong after FROM or after table. Can you confirm my understanding of where the four properties can be used: joinOrder can be used with a FROM clause; index, constraint, and joinStrategy can be used only within a TableExpression. Is that correct? > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-878) documentation to address DERBY-573
[ http://issues.apache.org/jira/browse/DERBY-878?page=all ] Eric Radzinski closed DERBY-878: Resolution: Duplicate closing this issue. It's a duplicate of Derby-855 > documentation to address DERBY-573 > -- > > Key: DERBY-878 > URL: http://issues.apache.org/jira/browse/DERBY-878 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.0.2.0 > Reporter: Eric Radzinski > Assignee: Eric Radzinski > > documentation to address optimizer hints that were added by DERBY-573 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DERBY-878) documentation to address DERBY-573
documentation to address DERBY-573 -- Key: DERBY-878 URL: http://issues.apache.org/jira/browse/DERBY-878 Project: Derby Type: Sub-task Components: Documentation Versions: 10.0.2.0 Reporter: Eric Radzinski Assigned to: Eric Radzinski documentation to address optimizer hints that were added by DERBY-573 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-855) Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ] Eric Radzinski reassigned DERBY-855: Assign To: Eric Radzinski > Document optimizer overrides which were introduced in 10.2 > -- > > Key: DERBY-855 > URL: http://issues.apache.org/jira/browse/DERBY-855 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assignee: Eric Radzinski > Fix For: 10.2.0.0 > > Optimizer overrides support in Derby was added as jira entry DERBY-573. Eric > Radzinski is working on the documentation part of the feature. This issue is > to keep track of documentation changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-678) derby documentation does not reflect changes to update lock behavior
[ http://issues.apache.org/jira/browse/DERBY-678?page=all ] Eric Radzinski updated DERBY-678: - Attachment: derby678.diff cdevconcepts842385.html Attached patch address the bug that's identified in this issue. HTML file is included for review. > derby documentation does not reflect changes to update lock behavior > > > Key: DERBY-678 > URL: http://issues.apache.org/jira/browse/DERBY-678 > Project: Derby > Type: Bug > Components: Documentation > Versions: 10.0.2.0 > Reporter: Mike Matrigali > Fix For: 10.2.0.0 > Attachments: cdevconcepts842385.html, derby678.diff > > The following section in the developers guide on update locks needs to be > changed from: > When a user-defined update cursor (created with the FOR UPDATE clause) reads > data, its transaction obtains an update lock on the data. If the user-defined > update cursor updates the data, the update lock is converted to an exclusive > lock. If the cursor does not update the row, when the transaction steps > through to the next row, transactions using the TRANSACTION_READ_COMMITTED > isolation level release the lock, and transactions using the > TRANSACTION_SERIALIZABLE or TRANSACTION_REPEATABLE_READ isolation level > downgrade it to a shared lock until the transaction is committed. (For update > locks, the TRANSACTION_READ_UNCOMMITTED isolation level acts the same way as > TRANSACTION_READ_COMMITTED.) > to: > When a user-defined update cursor (created with the FOR UPDATE clause) reads > data, its transaction obtains an update lock on the data. If the user-defined > update cursor updates the data, the update lock is converted to an exclusive > lock. If the cursor does not update the row, when the transaction steps > through to the next row, transactions using the TRANSACTION_READ_COMMITTED > isolation level release the lock. > (For update locks, the TRANSACTION_READ_UNCOMMITTED isolation level acts the > same way as TRANSACTION_READ_COMMITTED.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-869) documentation to address Derby-783
[ http://issues.apache.org/jira/browse/DERBY-869?page=all ] Eric Radzinski reassigned DERBY-869: Assign To: Eric Radzinski > documentation to address Derby-783 > -- > > Key: DERBY-869 > URL: http://issues.apache.org/jira/browse/DERBY-869 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.0.2.0 > Reporter: Eric Radzinski > Assignee: Eric Radzinski > Attachments: derby869.diff, rrefsqlj81859.html > > document changes to ALTER TABLE syntax to address Derby-783 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-869) documentation to address Derby-783
[ http://issues.apache.org/jira/browse/DERBY-869?page=all ] Eric Radzinski updated DERBY-869: - Attachment: derby869.diff rrefsqlj81859.html Attached patch address changes to ALTER TABLE column-alteration functionality that was introduced by Derby-783. HTML file included for review. > documentation to address Derby-783 > -- > > Key: DERBY-869 > URL: http://issues.apache.org/jira/browse/DERBY-869 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.0.2.0 > Reporter: Eric Radzinski > Attachments: derby869.diff, rrefsqlj81859.html > > document changes to ALTER TABLE syntax to address Derby-783 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-869) documentation to address Derby-783
[ http://issues.apache.org/jira/browse/DERBY-869?page=comments#action_12363899 ] Eric Radzinski commented on DERBY-869: -- Attached patch address changes to the ALTER TABLE column-alteration functionality that was introduced by Derby-783. HTML file included for review... > documentation to address Derby-783 > -- > > Key: DERBY-869 > URL: http://issues.apache.org/jira/browse/DERBY-869 > Project: Derby > Type: Sub-task > Components: Documentation > Versions: 10.0.2.0 > Reporter: Eric Radzinski > Attachments: derby869.diff, rrefsqlj81859.html > > document changes to ALTER TABLE syntax to address Derby-783 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DERBY-869) documentation to address Derby-783
documentation to address Derby-783 -- Key: DERBY-869 URL: http://issues.apache.org/jira/browse/DERBY-869 Project: Derby Type: Sub-task Components: Documentation Versions: 10.0.2.0 Reporter: Eric Radzinski document changes to ALTER TABLE syntax to address Derby-783 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-701) Java 2 security policy file examples don't work -- are missing a needed line
[ http://issues.apache.org/jira/browse/DERBY-701?page=all ]
Eric Radzinski updated DERBY-701:
-
Attachment: derby701.diff
derby701_html_files.zip
Attached patch applies the requested change to the three Java 2 security policy
file examples as requested. HTML files are included for review.
> Java 2 security policy file examples don't work -- are missing a needed line
>
>
> Key: DERBY-701
> URL: http://issues.apache.org/jira/browse/DERBY-701
> Project: Derby
> Type: Bug
> Components: Documentation
> Versions: 10.1.1.1
> Reporter: Jean T. Anderson
> Priority: Minor
> Attachments: derby701.diff, derby701_html_files.zip
>
> These security policy file examples don't work as is:
>http://db.apache.org/derby/docs/dev/devguide/rdevcsecure871406.html
>http://db.apache.org/derby/docs/dev/devguide/rdevcsecure871422.html
>http://db.apache.org/derby/docs/dev/devguide/rdevcsecure871439.html
> Each example needs this additional line:
>permission java.io.FilePermission "${derby.system.home}","read";
> The email thread is here:
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200511.mbox/[EMAIL
> PROTECTED]
> To show one of the examples, here is the current text for Example 1:
> grant codeBase "file://f:/derby/lib/derby.jar" {
> permission java.lang.RuntimePermission "createClassLoader";
> permission java.util.PropertyPermission "derby.*", "read";
> permission java.io.FilePermission "${derby.system.home}${/}-",
> "read,write,delete";
> };
> It needs to be this instead:
> grant codeBase "file://f:/derby/lib/derby.jar" {
>permission java.lang.RuntimePermission "createClassLoader";
>permission java.util.PropertyPermission "derby.*", "read";
>permission java.io.FilePermission "${derby.system.home}","read";
>permission java.io.FilePermission
> "${derby.system.home}${/}-","read,write,delete";
> };
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-679) the lock compatibility table in developers guide needs to be updated
[ http://issues.apache.org/jira/browse/DERBY-679?page=all ] Eric Radzinski updated DERBY-679: - Attachment: derby679.diff rdevconcepts2462.html Attached patch applies the requested change to the Lock Compatibility Matrix table (Shared row, Updated column changed from - to +) as requested. HTML file included for review... > the lock compatibility table in developers guide needs to be updated > > > Key: DERBY-679 > URL: http://issues.apache.org/jira/browse/DERBY-679 > Project: Derby > Type: Bug > Components: Documentation > Versions: 10.0.2.0 > Reporter: Mike Matrigali > Fix For: 10.2.0.0 > Attachments: derby679.diff, rdevconcepts2462.html > > In the lock compatibility table in the developers guide > (http://db.apache.org/derby/docs/10.1/devguide/rdevconcepts2462.html) > The middle cell in the top row should have a + rather than a - (ie. > shared/update is compatible -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
