[jira] Closed: (DERBY-460) Create error message documentation out of code
[ http://issues.apache.org/jira/browse/DERBY-460?page=all ] Jeff Levitt closed DERBY-460: - Resolution: Duplicate David Van Couvering long ago submitted a script that takes care of this, so I am cancelling my own bug Create error message documentation out of code -- Key: DERBY-460 URL: http://issues.apache.org/jira/browse/DERBY-460 Project: Derby Type: Improvement Components: Build tools Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 As David suggested in the following thread: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200507.mbox/[EMAIL PROTECTED] We need a way to generate a DITA file for the Reference Manual from the messages themselves, so that when new messages are added or changes are made, they are propogated to the documentation. The requirements are: - Some way of keeping metadata for the DITA file (parameter values, user response, explanation) in comments within the messages file, or perhaps using an XML document to store the data and the strings? - A script or xsl transform that reads the messages and generates the DITA file, adding the metadata where necessary. - A script to do a one-time conversion of the DITA file to the messages file (whether it be the current method of storing message plus comments or an XML file) so that existing messages will be in the new format. Then, any new messages must follow the format. -- 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-1268) Add description of derby.drda.streamOutBufferSize to Derby Server and Administration Guide
[ http://issues.apache.org/jira/browse/DERBY-1268?page=comments#action_12414656 ] Jeff Levitt commented on DERBY-1268: Looks great! Just a legal nit (I think). Since this is a newly contributed source file in 2006, shouldn't the Apache copyright statement at the beginning of the dita source file be 2006 instead of 2005? Add description of derby.drda.streamOutBufferSize to Derby Server and Administration Guide Key: DERBY-1268 URL: http://issues.apache.org/jira/browse/DERBY-1268 Project: Derby Type: Sub-task Components: Documentation Reporter: Tomohito Nakayama Assignee: Tomohito Nakayama Attachments: DERBY-1268.patch, DERBY-1268_2.patch New property , derby.drda.streamOutBufferSize was added in DERBY-326. We need to reflect this modification to Derby Server and Administration Guide url of the repository : https://svn.apache.org/repos/asf/db/derby/docs/trunk/src/adminguide/tadminconfigsettingnetwrokserverproperties.dita url of html rendered : http://db.apache.org/derby/docs/10.1/adminguide/tadminconfigsettingnetwrokserverproperties.html -- 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-1359) Developers guide: example showing shut down of Derby system should not contain a database name
[ http://issues.apache.org/jira/browse/DERBY-1359?page=all ] Jeff Levitt updated DERBY-1359: --- Derby Info: [Patch Available] Developers guide: example showing shut down of Derby system should not contain a database name -- Key: DERBY-1359 URL: http://issues.apache.org/jira/browse/DERBY-1359 Project: Derby Type: Bug Components: Documentation Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.1.2.2, 10.1.2.3, 10.1.2.4, 10.2.0.0, 10.1.3.0 Reporter: Olav Sandstaa Priority: Trivial Attachments: derby1359.diff, tdevdvlp20349.html In the Developers Guide the chapter Shutting Down the System gives the following command to shut down the Derby system: DriverManager.getConnection(jdbc:derby:cs;shutdown=true); This command should not include the name of a database (cs). The correct command should be: DriverManager.getConnection(jdbc:derby:;shutdown=true); -- 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-283) On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server .
[ http://issues.apache.org/jira/browse/DERBY-283?page=comments#action_12373035 ] Jeff Levitt commented on DERBY-283: --- If there are no objections with this patch, can it be committed? I have called for a review several times with no response, so I am assuming no one has any negative votes. On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server . -- Key: DERBY-283 URL: http://issues.apache.org/jira/browse/DERBY-283 Project: Derby Type: Bug Components: Network Server Versions: 10.0.2.1 Reporter: Manjula Kutty Priority: Minor Attachments: derby283.diff, tadminconfigipx.html On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server . -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true This is a Windows OS problem and have to track to to see when MS is going to fix and then make the appropriate changes in our docs -- 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-724) Derby supports JDBC date escape format but this is not documented
[
http://issues.apache.org/jira/browse/DERBY-724?page=comments#action_12373036 ]
Jeff Levitt commented on DERBY-724:
---
If there are no objections with this patch, can it be committed? I have called
for a review several times with no response, so I am assuming no one has any
negative votes.
Derby supports JDBC date escape format but this is not documented
-
Key: DERBY-724
URL: http://issues.apache.org/jira/browse/DERBY-724
Project: Derby
Type: Bug
Components: Documentation
Versions: 10.1.2.1
Reporter: Daniel John Debrunner
Priority: Minor
Attachments: derby724.diff, rrefjdbcescapedate.html
The JDBC escape format section in the reference manual, page 198 in the pdf
for 10.1, documents the time and timestamp support, but not the date format.
{d '-mm-dd'}
e.g.
{d '1995-12-19'}
See section 13.4.2 of JDBC 3.0 specifiction.
--
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-1123) Derby Reference Manual - SYSCS_UTIL.SYSCS_CHECK_TABLE
[ http://issues.apache.org/jira/browse/DERBY-1123?page=all ] Jeff Levitt updated DERBY-1123: --- Attachment: SYSCS_CHECK_TABLE_JEFF_modified.diff Here's my own patch based on Halley's patch. I just thought we should add the singular table to the sentences. So now it checks the table and indexes, instead of just the indexes. Derby Reference Manual - SYSCS_UTIL.SYSCS_CHECK_TABLE - Key: DERBY-1123 URL: http://issues.apache.org/jira/browse/DERBY-1123 Project: Derby Type: Bug Components: Documentation Versions: 10.1.2.3 Environment: DITA files Reporter: Halley Pacheco de Oliveira Fix For: 10.2.0.0 Attachments: SYSCS_CHECK_TABLE.diff, SYSCS_CHECK_TABLE_JEFF_modified.diff In SYSCS_UTIL.SYSCS_CHECK_TABLE is written: The SYSCS_UTIL.SYSCS_CHECK_TABLE function checks the specified table, ensuring that all of its indexes are consistent with the base table. When tables are consistent, the method returns a SMALLINT with value 1. If the tables are inconsistent, the function will throw an exception. I think that in the last two sentences of this paragraph the word tables should be changed to indexes, because it is the indexes that are being tested for consistency with the base table, and to maintain the word tables it should be in the singular (table) and not in the plural (tables), because the function tests just one table at each call. So the patched paragraph becomes: The SYSCS_UTIL.SYSCS_CHECK_TABLE function checks the specified table, ensuring that all of its indexes are consistent with the base table. When indexes are consistent, the method returns a SMALLINT with value 1. If the indexes are inconsistent, the function will throw an exception. -- 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-1150) [web] Add new section to DITA source page describing how to edit DITA files
[web] Add new section to DITA source page describing how to edit DITA files --- Key: DERBY-1150 URL: http://issues.apache.org/jira/browse/DERBY-1150 Project: Derby Type: Improvement Components: Web Site Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 We need a new section on the Derby DITA Source page: http://db.apache.org/derby/manuals/dita.html The new section needs to describe how to edit DITA files, use XML editors, provide some example XML editors, and provide the new website for learning and using DITA resources at http://dita.xml.org. -- 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-1150) [web] Add new section to DITA source page describing how to edit DITA files
[ http://issues.apache.org/jira/browse/DERBY-1150?page=all ] Jeff Levitt updated DERBY-1150: --- Attachment: derby1150.diff The attached patch creates the new section as described. [web] Add new section to DITA source page describing how to edit DITA files --- Key: DERBY-1150 URL: http://issues.apache.org/jira/browse/DERBY-1150 Project: Derby Type: Improvement Components: Web Site Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 Attachments: derby1150.diff We need a new section on the Derby DITA Source page: http://db.apache.org/derby/manuals/dita.html The new section needs to describe how to edit DITA files, use XML editors, provide some example XML editors, and provide the new website for learning and using DITA resources at http://dita.xml.org. -- 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-1057) documentation to address Grant/Revoke (Derby-464)
[ http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12371456 ] Jeff Levitt commented on DERBY-1057: Has anyone had a chance to look at the grant/revoke doc patches? It would be cool if grant/revoke could get committed soon, but if there is feedback to be made, we should get it now...Thanks! 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_devguide.diff, derby1057_devguide_html.zip, 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] Updated: (DERBY-1057) documentation to address Grant/Revoke (Derby-464)
[ http://issues.apache.org/jira/browse/DERBY-1057?page=all ] Jeff Levitt updated DERBY-1057: --- Attachment: derby1057_devguide.diff derby1057_devguide_html.zip The patch I am attaching (derby1057_devguide.diff) complements Eric Radzinski's patch for the reference manual. My patch makes changes to the User Authorization section of the Developer's Guide. I have included an html zip file including sample output for the Developer's Guide relevant html files. I would appreciate any feedbackso that we can get these two patches committed soon. Remember that the two patches complement each other, and that together, they patch the ref guide and dev guide to include the total information needed for grant/revoke. Also, in the devguide, note that i did not remove information about the legacy authorization functionality, as that still works. I simply integrated the grant/revoke information into it in the section on User Authorization. Thanks again in advance for your quick feedback! 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_devguide.diff, derby1057_devguide_html.zip, 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] Commented: (DERBY-539) Update the Create Index statement in the Derby documentation with additional information
[ http://issues.apache.org/jira/browse/DERBY-539?page=comments#action_12370408 ] Jeff Levitt commented on DERBY-539: --- Can someone take a look at the most recent patch so it can commit if it looks good? Thanks! Update the Create Index statement in the Derby documentation with additional information Key: DERBY-539 URL: http://issues.apache.org/jira/browse/DERBY-539 Project: Derby Type: Improvement Components: Documentation Reporter: Susan Cline Priority: Minor Attachments: derby539-take2.diff, derby539.diff, rrefsqlj20937.html In the 'Create Index' statement documentation of the 10.1 Reference Guide (derby/docs/10.1/ref/rrefsqlj20937.html) this statement is made about creating indexes and constraints: Indexes and constraints Unique, primary key, and foreign key constraints generate indexes that enforce or back the constraint (and are thus sometimes called backing indexes). If a column or set of columns has a UNIQUE or PRIMARY KEY constraint on it, you can not create an index on those columns. Derby has already created it for you with a system-generated name. This is true, but I think it can be expanded upon to be clearer. A suggestion for this is below: Indexes and constraints Unique, primary key, and foreign key constraints generate indexes that enforce or back the constraint (and are thus sometimes called backing indexes). If a column or set of columns has a PRIMARY KEY constraint on it, you can not create an index on those columns. If a column or set of columns has a UNIQUE constraint on it, you can not create an index on those columns, but you can create a PRIMARY KEY constraint on it. Addtionally, if this is the case, a backing index will be created for the PRIMARY KEY constraint so two indexes will now exist on the column or set of columns that had the UNIQUE constraint on it. This issue came up when I noticed that I could create a unique index on a column, then create a PK on that column. When I used a tool to generate DDL for the table I noticed one constraint and two indexes on the column which didn't make sense at first when reading the existing documentation. With the additional information above I think it explains the real behaviour better. -- 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-769) CLOB and BLOB descriptions do not specify the default length
[ http://issues.apache.org/jira/browse/DERBY-769?page=comments#action_12370409 ] Jeff Levitt commented on DERBY-769: --- Can this be committed by a committer please? Thanks! CLOB and BLOB descriptions do not specify the default length Key: DERBY-769 URL: http://issues.apache.org/jira/browse/DERBY-769 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0 Reporter: Daniel John Debrunner Priority: Trivial Attachments: derby769-2.diff, derby769.diff, rrefblob.html, rrefclob.html BLOB without a length has a default length of 1 mega byte, ie. same as BLOB(1M) CLOB without a length has a default length of 1 mega characters, ie. same as CLOB(1M) http://db.apache.org/derby/docs/10.1/ref/rrefblob.html http://db.apache.org/derby/docs/10.1/ref/rrefclob.html -- 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-1077) [doc] Add relationship table for Developer's Guide
[ http://issues.apache.org/jira/browse/DERBY-1077?page=comments#action_12370410 ] Jeff Levitt commented on DERBY-1077: Has someone had a chance to look at this patch? If so, can you comment on it ASAP? The sooner it can get committed, the better. Thanks, Jeff [doc] Add relationship table for Developer's Guide -- Key: DERBY-1077 URL: http://issues.apache.org/jira/browse/DERBY-1077 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Assignee: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 Attachments: devguidereltable.diff I am creating this issue to submit a patch for the Developer's Guide doc source. This patch fixes the same problems in the Dev Guide that Derby-489 fixed in the Getting Started Guide having to do with related links: http://issues.apache.org/jira/browse/DERBY-489 The relevant discussion as to why these patches are necessary is discussed there as well. -- 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-724) Derby supports JDBC date escape format but this is not documented
[
http://issues.apache.org/jira/browse/DERBY-724?page=comments#action_12370411 ]
Jeff Levitt commented on DERBY-724:
---
Can someone comment on this patch so that it can be committed if all looks OK?
Thanks!
Derby supports JDBC date escape format but this is not documented
-
Key: DERBY-724
URL: http://issues.apache.org/jira/browse/DERBY-724
Project: Derby
Type: Bug
Components: Documentation
Versions: 10.1.2.1
Reporter: Daniel John Debrunner
Priority: Minor
Attachments: derby724.diff, rrefjdbcescapedate.html
The JDBC escape format section in the reference manual, page 198 in the pdf
for 10.1, documents the time and timestamp support, but not the date format.
{d '-mm-dd'}
e.g.
{d '1995-12-19'}
See section 13.4.2 of JDBC 3.0 specifiction.
--
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-283) On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server .
[ http://issues.apache.org/jira/browse/DERBY-283?page=comments#action_12370412 ] Jeff Levitt commented on DERBY-283: --- Can someone take a look at this patch and comment on it so that it can be committed if all looks OK? Thanks! On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server . -- Key: DERBY-283 URL: http://issues.apache.org/jira/browse/DERBY-283 Project: Derby Type: Bug Components: Network Server Versions: 10.0.2.1 Reporter: Manjula Kutty Priority: Minor Attachments: derby283.diff, tadminconfigipx.html On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server . -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true This is a Windows OS problem and have to track to to see when MS is going to fix and then make the appropriate changes in our docs -- 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_12369529 ] Jeff Levitt commented on DERBY-916: --- Can a committer please commit this? It looks like there are no objections to the latest patch. Thanks Suresh! 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-2.diff, derby916-2html.zip, 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-283) On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server .
[ http://issues.apache.org/jira/browse/DERBY-283?page=all ] Jeff Levitt updated DERBY-283: -- Attachment: derby283.diff tadminconfigipx.html Attached patch adds the information to the Admin Guide in the section about Starting the Network Server. HTML output included for review. Please let me know if it looks good so a committer can commit. Thanks! On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server . -- Key: DERBY-283 URL: http://issues.apache.org/jira/browse/DERBY-283 Project: Derby Type: Bug Components: Network Server Versions: 10.0.2.1 Reporter: Manjula Kutty Priority: Minor Attachments: derby283.diff, tadminconfigipx.html On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server . -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true This is a Windows OS problem and have to track to to see when MS is going to fix and then make the appropriate changes in our docs -- 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-60) Documentation refers to SYSIBM system schema
[ http://issues.apache.org/jira/browse/DERBY-60?page=comments#action_12369125 ] Jeff Levitt commented on DERBY-60: -- So I am going to create a page in the Ref manual that lists system schemas, and I am going to include the following: APP NULLID SQLJ SYS SYSCAT SYSCS_DIAG SYSCS_UTIL SYSFUN SYSIBM SYSPROC SYSSTAT Is there any information I should include about them or about these in general? Thanks! Documentation refers to SYSIBM system schema Key: DERBY-60 URL: http://issues.apache.org/jira/browse/DERBY-60 Project: Derby Type: Bug Components: Documentation Reporter: John Sisson Priority: Trivial http://incubator.apache.org/derby/manuals/tools/tools109.html refers to the SYSIBM system schema as an example, but SYSIBM is not mentioned anywhere else in the Derby documentation (when I searched for it). -- 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-724) Derby supports JDBC date escape format but this is not documented
[ http://issues.apache.org/jira/browse/DERBY-724?page=all ]
Jeff Levitt updated DERBY-724:
--
Attachment: derby724.diff
rrefjdbcescapedate.html
Attached patch adds a new topic in the JDBC escaped formats area of the ref
manual. The new topic describes the date escaped syntax. The attached output
file is included for review. Please let me know if there is anything else
needed to do or if this is ready for a commit. Thanks!
Derby supports JDBC date escape format but this is not documented
-
Key: DERBY-724
URL: http://issues.apache.org/jira/browse/DERBY-724
Project: Derby
Type: Bug
Components: Documentation
Versions: 10.1.2.1
Reporter: Daniel John Debrunner
Priority: Minor
Attachments: derby724.diff, rrefjdbcescapedate.html
The JDBC escape format section in the reference manual, page 198 in the pdf
for 10.1, documents the time and timestamp support, but not the date format.
{d '-mm-dd'}
e.g.
{d '1995-12-19'}
See section 13.4.2 of JDBC 3.0 specifiction.
--
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_12368962 ]
Jeff Levitt commented on DERBY-571:
---
I looked, and our current doc does not have any information for any of the now
replaced org.apache.derby.diag.whatever tables. Do we want a new section to
document the SYSCS_DIAG.whatever tanles, and if so, where and in which
manual? Or is the javadoc satisfactory?
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] Commented: (DERBY-931) Until Derby-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly
[ http://issues.apache.org/jira/browse/DERBY-931?page=comments#action_12368909 ] Jeff Levitt commented on DERBY-931: --- OK thanks. So do I just want to add a bullet that says that setReadOnly ignores options in a client-server mode, but works fine in embedded mode? Until Derby-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly Key: DERBY-931 URL: http://issues.apache.org/jira/browse/DERBY-931 Project: Derby Type: Sub-task Components: Documentation Versions: 10.0.2.1 Reporter: Mamta A. Satoor Derby 911 Connection.setReadOnly is a no-op in Network Client. It works fine with embedded client. has more details on this issue but basically, we should document the difference in behavior for setReadOnly between Network Driver and Embedded Driver. -- 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-1077) [doc] Add relationship table for Developer's Guide
[doc] Add relationship table for Developer's Guide -- Key: DERBY-1077 URL: http://issues.apache.org/jira/browse/DERBY-1077 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Assigned to: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 I am creating this issue to submit a patch for the Developer's Guide doc source. This patch fixes the same problems in the Dev Guide that Derby-489 fixed in the Getting Started Guide having to do with related links: http://issues.apache.org/jira/browse/DERBY-489 The relevant discussion as to why these patches are necessary is discussed there as well. -- 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-1077) [doc] Add relationship table for Developer's Guide
[ http://issues.apache.org/jira/browse/DERBY-1077?page=all ] Jeff Levitt updated DERBY-1077: --- Attachment: devguidereltable.diff Attached patch fixes the links in the Dev Guide as discussed. A relationship table has been added to keep linking within the guide easy. I created sample output on my own server for review here: http://derby.mylevita.com/devguide/ [doc] Add relationship table for Developer's Guide -- Key: DERBY-1077 URL: http://issues.apache.org/jira/browse/DERBY-1077 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Assignee: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 Attachments: devguidereltable.diff I am creating this issue to submit a patch for the Developer's Guide doc source. This patch fixes the same problems in the Dev Guide that Derby-489 fixed in the Getting Started Guide having to do with related links: http://issues.apache.org/jira/browse/DERBY-489 The relevant discussion as to why these patches are necessary is discussed there as well. -- 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 ] Jeff Levitt updated DERBY-916: -- Attachment: derby916-2.diff derby916-2html.zip I went ahead and made these final minor changes to the patch because it was so close to commit. The derby916-2.diff is the new patch file, and contains the latest comments from Suresh. The derby916-2html.zip file contains new html ouput files for review. Thanks! 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-2.diff, derby916-2html.zip, 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-769) CLOB and BLOB descriptions do not specify the default length
[ http://issues.apache.org/jira/browse/DERBY-769?page=all ] Jeff Levitt updated DERBY-769: -- Attachment: derby769.diff rrefblob.html rrefclob.html Attached patch (derby769.diff) adds a default section in both topics, each saying that the default length for these types is one megabyte if no length is specified, See html output files included for review. Thanks! CLOB and BLOB descriptions do not specify the default length Key: DERBY-769 URL: http://issues.apache.org/jira/browse/DERBY-769 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0 Reporter: Daniel John Debrunner Priority: Trivial Attachments: derby769.diff, rrefblob.html, rrefclob.html BLOB without a length has a default length of 1 mega byte, ie. same as BLOB(1M) CLOB without a length has a default length of 1 mega characters, ie. same as CLOB(1M) http://db.apache.org/derby/docs/10.1/ref/rrefblob.html http://db.apache.org/derby/docs/10.1/ref/rrefclob.html -- 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-769) CLOB and BLOB descriptions do not specify the default length
[ http://issues.apache.org/jira/browse/DERBY-769?page=all ] Jeff Levitt updated DERBY-769: -- Attachment: derby769-2.diff rrefblob.html rrefclob.html Thanks Dan, Attached patch (derby769-2.diff) takes care of those syntax errors, and htmlfiles are once again included for review. Thanks for the quick feedback! Letme know if everything looks OK. CLOB and BLOB descriptions do not specify the default length Key: DERBY-769 URL: http://issues.apache.org/jira/browse/DERBY-769 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0 Reporter: Daniel John Debrunner Priority: Trivial Attachments: derby769-2.diff, derby769.diff, rrefblob.html, rrefclob.html BLOB without a length has a default length of 1 mega byte, ie. same as BLOB(1M) CLOB without a length has a default length of 1 mega characters, ie. same as CLOB(1M) http://db.apache.org/derby/docs/10.1/ref/rrefblob.html http://db.apache.org/derby/docs/10.1/ref/rrefclob.html -- 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-769) CLOB and BLOB descriptions do not specify the default length
[ http://issues.apache.org/jira/browse/DERBY-769?page=all ] Jeff Levitt updated DERBY-769: -- Attachment: (was: rrefblob.html) CLOB and BLOB descriptions do not specify the default length Key: DERBY-769 URL: http://issues.apache.org/jira/browse/DERBY-769 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0 Reporter: Daniel John Debrunner Priority: Trivial Attachments: derby769-2.diff, derby769.diff, rrefblob.html, rrefclob.html BLOB without a length has a default length of 1 mega byte, ie. same as BLOB(1M) CLOB without a length has a default length of 1 mega characters, ie. same as CLOB(1M) http://db.apache.org/derby/docs/10.1/ref/rrefblob.html http://db.apache.org/derby/docs/10.1/ref/rrefclob.html -- 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-769) CLOB and BLOB descriptions do not specify the default length
[ http://issues.apache.org/jira/browse/DERBY-769?page=all ] Jeff Levitt updated DERBY-769: -- Attachment: (was: rrefclob.html) CLOB and BLOB descriptions do not specify the default length Key: DERBY-769 URL: http://issues.apache.org/jira/browse/DERBY-769 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0 Reporter: Daniel John Debrunner Priority: Trivial Attachments: derby769-2.diff, derby769.diff, rrefblob.html, rrefclob.html BLOB without a length has a default length of 1 mega byte, ie. same as BLOB(1M) CLOB without a length has a default length of 1 mega characters, ie. same as CLOB(1M) http://db.apache.org/derby/docs/10.1/ref/rrefblob.html http://db.apache.org/derby/docs/10.1/ref/rrefclob.html -- 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-671) Clob.getCharacterStream documented as not supported when it actually is
[ http://issues.apache.org/jira/browse/DERBY-671?page=all ] Jeff Levitt updated DERBY-671: -- Attachment: derby671.diff rrefjdbc96386.html This patch removes the offending NOT SUPPORTED text from the file. If this looks OK, please post approval so the patch can be committed. Thanks! Clob.getCharacterStream documented as not supported when it actually is --- Key: DERBY-671 URL: http://issues.apache.org/jira/browse/DERBY-671 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0 Reporter: Lars Clausen Priority: Minor Attachments: derby671.diff, rrefjdbc96386.html In the online documentation for Blob and Clob at http://db.apache.org/derby/docs/10.1/ref/rrefjdbc96386.html#rrefjdbc96386, the Clob.getCharacterStream() method is listed as NOT SUPPORTED[sic], but it is in fact supported, at least in the embedded driver. This misleading documentation led us to use an alternative and noninternationalizable way of reading clobs, so it is not just a cosmetic issue. -- 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-671) Clob.getCharacterStream documented as not supported when it actually is
[ http://issues.apache.org/jira/browse/DERBY-671?page=comments#action_12368810 ] Jeff Levitt commented on DERBY-671: --- Hmmm, I just openedit again. It looksfine. Can a committer see if the patch looks good to them, and commit if so? Thanks! Clob.getCharacterStream documented as not supported when it actually is --- Key: DERBY-671 URL: http://issues.apache.org/jira/browse/DERBY-671 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0 Reporter: Lars Clausen Priority: Minor Attachments: derby671.diff, rrefjdbc96386.html In the online documentation for Blob and Clob at http://db.apache.org/derby/docs/10.1/ref/rrefjdbc96386.html#rrefjdbc96386, the Clob.getCharacterStream() method is listed as NOT SUPPORTED[sic], but it is in fact supported, at least in the embedded driver. This misleading documentation led us to use an alternative and noninternationalizable way of reading clobs, so it is not just a cosmetic issue. -- 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-539) Update the Create Index statement in the Derby documentation with additional information
[ http://issues.apache.org/jira/browse/DERBY-539?page=all ] Jeff Levitt updated DERBY-539: -- Attachment: derby539-take2.diff rrefsqlj20937.html My second attempt at this patch. Derby539-take2.diff includes Dan's comment. I added the sentence he requests and left the rest of the paragraph alone. HTML file included for review. Update the Create Index statement in the Derby documentation with additional information Key: DERBY-539 URL: http://issues.apache.org/jira/browse/DERBY-539 Project: Derby Type: Improvement Components: Documentation Reporter: Susan Cline Priority: Minor Attachments: derby539-take2.diff, derby539.diff, rrefsqlj20937.html, rrefsqlj20937.html In the 'Create Index' statement documentation of the 10.1 Reference Guide (derby/docs/10.1/ref/rrefsqlj20937.html) this statement is made about creating indexes and constraints: Indexes and constraints Unique, primary key, and foreign key constraints generate indexes that enforce or back the constraint (and are thus sometimes called backing indexes). If a column or set of columns has a UNIQUE or PRIMARY KEY constraint on it, you can not create an index on those columns. Derby has already created it for you with a system-generated name. This is true, but I think it can be expanded upon to be clearer. A suggestion for this is below: Indexes and constraints Unique, primary key, and foreign key constraints generate indexes that enforce or back the constraint (and are thus sometimes called backing indexes). If a column or set of columns has a PRIMARY KEY constraint on it, you can not create an index on those columns. If a column or set of columns has a UNIQUE constraint on it, you can not create an index on those columns, but you can create a PRIMARY KEY constraint on it. Addtionally, if this is the case, a backing index will be created for the PRIMARY KEY constraint so two indexes will now exist on the column or set of columns that had the UNIQUE constraint on it. This issue came up when I noticed that I could create a unique index on a column, then create a PK on that column. When I used a tool to generate DDL for the table I noticed one constraint and two indexes on the column which didn't make sense at first when reading the existing documentation. With the additional information above I think it explains the real behaviour better. -- 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-539) Update the Create Index statement in the Derby documentation with additional information
[ http://issues.apache.org/jira/browse/DERBY-539?page=all ] Jeff Levitt updated DERBY-539: -- Attachment: (was: rrefsqlj20937.html) Update the Create Index statement in the Derby documentation with additional information Key: DERBY-539 URL: http://issues.apache.org/jira/browse/DERBY-539 Project: Derby Type: Improvement Components: Documentation Reporter: Susan Cline Priority: Minor Attachments: derby539-take2.diff, derby539.diff, rrefsqlj20937.html In the 'Create Index' statement documentation of the 10.1 Reference Guide (derby/docs/10.1/ref/rrefsqlj20937.html) this statement is made about creating indexes and constraints: Indexes and constraints Unique, primary key, and foreign key constraints generate indexes that enforce or back the constraint (and are thus sometimes called backing indexes). If a column or set of columns has a UNIQUE or PRIMARY KEY constraint on it, you can not create an index on those columns. Derby has already created it for you with a system-generated name. This is true, but I think it can be expanded upon to be clearer. A suggestion for this is below: Indexes and constraints Unique, primary key, and foreign key constraints generate indexes that enforce or back the constraint (and are thus sometimes called backing indexes). If a column or set of columns has a PRIMARY KEY constraint on it, you can not create an index on those columns. If a column or set of columns has a UNIQUE constraint on it, you can not create an index on those columns, but you can create a PRIMARY KEY constraint on it. Addtionally, if this is the case, a backing index will be created for the PRIMARY KEY constraint so two indexes will now exist on the column or set of columns that had the UNIQUE constraint on it. This issue came up when I noticed that I could create a unique index on a column, then create a PK on that column. When I used a tool to generate DDL for the table I noticed one constraint and two indexes on the column which didn't make sense at first when reading the existing documentation. With the additional information above I think it explains the real behaviour better. -- 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_12368401 ]
Jeff Levitt commented on DERBY-571:
---
Eric recently asked if there are any tables to doc for this. I second that
motion. Could someone please provide information so that this can get
documented? Thanks!
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] Commented: (DERBY-627) Documentation needs to be updated with correct return type for COUNT functions
[ http://issues.apache.org/jira/browse/DERBY-627?page=comments#action_12368406 ] Jeff Levitt commented on DERBY-627: --- Could someone possibly review this patch please? Documentation needs to be updated with correct return type for COUNT functions -- Key: DERBY-627 URL: http://issues.apache.org/jira/browse/DERBY-627 Project: Derby Type: Bug Components: Documentation Versions: 10.2.0.0 Reporter: Deepa Remesh Priority: Minor Attachments: derby627.diff, rrefsqlj38716.html, rrefsqlj66113.html Derby Reference manual (Section 'Built-in functions', pg80-81) specifies the resulting data type of COUNT and COUNT(*) functions as BIGINT. Whereas, Derby returns INTEGER type for these functions. -- 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-629) Update documentation with correct default values for network server properties
[ http://issues.apache.org/jira/browse/DERBY-629?page=comments#action_12368407 ] Jeff Levitt commented on DERBY-629: --- Could someone please review this patch? Thanks in advance! Update documentation with correct default values for network server properties -- Key: DERBY-629 URL: http://issues.apache.org/jira/browse/DERBY-629 Project: Derby Type: Sub-task Components: Documentation Versions: 10.2.0.0 Reporter: Deepa Remesh Priority: Minor Attachments: derby629.diff, radmindrdamaxthreads.html, radmindrdaminthreads.html, radmindrdatimeslice.html Derby Server and Admin guide needs to be updated with the correct default value for the following network server properties: derby.drda.maxThreads derby.drda.minThreads derby.drda.timeSlice The default value for the above properties is 0. This information has to be updated in section 'Setting Network Server properties', pg 28 -29 -- 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-482) GENERATED BY DEFAULT option should be documented in Derby Tools and Utilities guide under Importing into tables with identity columns section.
[ http://issues.apache.org/jira/browse/DERBY-482?page=comments#action_12367232 ] Jeff Levitt commented on DERBY-482: --- Thats so strange. It did it to me too, and I looked at the original copy on my local machine and it looked fine. Mamtam when you try again, maybe just force it to an html extension by stripping the .xml it adds to the file name. Then open it up again and you should read it fine. GENERATED BY DEFAULT option should be documented in Derby Tools and Utilities guide under Importing into tables with identity columns section. Key: DERBY-482 URL: http://issues.apache.org/jira/browse/DERBY-482 Project: Derby Type: Improvement Components: Documentation Versions: 10.1.1.0 Reporter: Mamta A. Satoor Attachments: ctoolsimportidentitycol.html, derby482.diff Tomohito added support for import into identity columns by adding GENERATED BY DEFAULT option. This is documented in the Reference Guide but not in the Tools and Utilites Guide which is where a user would look for details on import. IMHO, there should be information about this in Importing into tables with identity columns section in Tools and Utilities Guide. -- 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-931) Until Derby-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly
[ http://issues.apache.org/jira/browse/DERBY-931?page=comments#action_12367064 ] Jeff Levitt commented on DERBY-931: --- The following section in the Server-Admin guide: http://db.apache.org/derby/docs/dev/adminguide/cadminapps.html describes differences between embedded and network server mode. Which topic in this section do you want to see this documented? Until Derby-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly Key: DERBY-931 URL: http://issues.apache.org/jira/browse/DERBY-931 Project: Derby Type: Sub-task Components: Documentation Versions: 10.0.2.1 Reporter: Mamta A. Satoor Derby 911 Connection.setReadOnly is a no-op in Network Client. It works fine with embedded client. has more details on this issue but basically, we should document the difference in behavior for setReadOnly between Network Driver and Embedded Driver. -- 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-809) Incorrect documentation for 'NetworkServerControl.logConnections(boolean)'
[ http://issues.apache.org/jira/browse/DERBY-809?page=all ] Jeff Levitt updated DERBY-809: -- Attachment: derby809.diff radminconfigdb2jdrdalogconnections.html tadminlogfile.html This patch complements the javadoc patch that Kristian submitted. The HTML output is included for review. If acceptable, the commits should port back to previous versions as well. Incorrect documentation for 'NetworkServerControl.logConnections(boolean)' -- Key: DERBY-809 URL: http://issues.apache.org/jira/browse/DERBY-809 Project: Derby Type: Bug Components: Documentation, Javadoc Versions: 10.0.2.1, 10.1.1.2, 10.1.2.1 Reporter: Kristian Waagan Priority: Minor Fix For: 10.2.0.0, 10.1.3.0 Attachments: DERBY-809-1a-javadoc.diff, DERBY-809-1a-javadoc.stat, derby809.diff, radminconfigdb2jdrdalogconnections.html, tadminlogfile.html The documentation for 'NetworkServerControl.logConnections(boolean)' states that Derby logs both connections and disconnections. As of 10.1.2.1 and (all) earlier releases, this is not true. The documentation should be corrected to avoid confusing users. The thought of adding logging of disconnections has also been posted on derby-dev. Byran Pendleton identified the following documentation with the incorrect description: http://db.apache.org/derby/javadoc/publishedapi/org/apache/derby/drda/NetworkServerControl.html http://db.apache.org/derby/docs/10.1/adminguide/radminconfigdb2jdrdalogconnections.html http://db.apache.org/derby/docs/10.0/manuals/admin/hubprnt23.html http://db.apache.org/derby/docs/10.1/adminguide/tadminlogfile.html Should we fix this in 10.0? If yes, please update fix versions for this issue. -- 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-870) Update documentation on setting up LDAP user authentication.
[ http://issues.apache.org/jira/browse/DERBY-870?page=comments#action_12366998 ] Jeff Levitt commented on DERBY-870: --- Has this been verified? If someone can confirm what is now needed, I would be happy to make a patch to update this part of the doc. Update documentation on setting up LDAP user authentication. Key: DERBY-870 URL: http://issues.apache.org/jira/browse/DERBY-870 Project: Derby Type: Improvement Components: Documentation Versions: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.2.0.0, 10.1.2.0, 10.1.1.1, 10.1.1.2, 10.1.2.1, 10.1.3.0, 10.1.2.2 Reporter: Sunitha Kambhampati Priority: Minor http://db.apache.org/derby/docs/dev/devguide/rdevcsecure608.html This talks about needing jndi.jar , ldap.jar and providerUtil.jar. I think this is not true anymore with the latest 1.4.2 vms atleast, and should be updated. It seems like with 1.4.2 etc, all these classes are in rt.jar. Need to verify and the doc needs to be updated. -- 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-820) path name incorrect in simple example doc
[ http://issues.apache.org/jira/browse/DERBY-820?page=all ] Jeff Levitt updated DERBY-820: -- Attachment: derby820.diff Pretty simple fix; I took out the program/ in the directory in the two places it was displayed. This is ready for a commitif no one objects... path name incorrect in simple example doc - Key: DERBY-820 URL: http://issues.apache.org/jira/browse/DERBY-820 Project: Derby Type: Bug Components: Documentation Versions: 10.1.2.1 Reporter: Tim Ellison Priority: Minor Attachments: derby820.diff The simple example doc (installed for me in file:///C:/db-derby-10.1.2.1-bin/demo/simple/example.html) contains a minor error: Section : How to run this sample application... and change directories to the %DERBY_INSTALL%\demo\programs\simple directory. should be and change directories to the %DERBY_INSTALL%\demo\simple directory. -- 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-784) Document predicate push down through union clause in Tuning guide where other similar optimizations are discussed.
[ http://issues.apache.org/jira/browse/DERBY-784?page=comments#action_12367000 ] Jeff Levitt commented on DERBY-784: --- I want to take a stab at a patch to the documentation for this, but in reading the other two connected issues, I wasn't able to discern what needed to be added/changed in the docs. Ifsomeone can provide me with alittle info to get started, I'd be happy to work on this... Document predicate push down through union clause in Tuning guide where other similar optimizations are discussed. -- Key: DERBY-784 URL: http://issues.apache.org/jira/browse/DERBY-784 Project: Derby Type: Sub-task Components: Documentation Versions: 10.1.2.0, 10.2.0.0 Reporter: Satheesh Bandaram Priority: Minor Fix For: 10.2.0.0 Document optimization implemented under DERBY-649 and DERBY-772 in tuning guide where similar such optimizations are discussed. -- 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-809) Incorrect documentation for 'NetworkServerControl.logConnections(boolean)'
[ http://issues.apache.org/jira/browse/DERBY-809?page=comments#action_12367001 ] Jeff Levitt commented on DERBY-809: --- Can someone confirm that the problem is that disconnections are documented as being logable when they are in fact not? If that's the case, I'd be happy to submit a patch that removes the references to disconnection logging. However, one of the links above is to the javadoc, which i am not familiar with, so I can patch the normal docs, but hopefully someone else can patch the javadoc. Incorrect documentation for 'NetworkServerControl.logConnections(boolean)' -- Key: DERBY-809 URL: http://issues.apache.org/jira/browse/DERBY-809 Project: Derby Type: Bug Components: Documentation, Javadoc Versions: 10.0.2.1, 10.1.1.2, 10.1.2.1 Reporter: Kristian Waagan Priority: Minor Fix For: 10.2.0.0, 10.1.3.0 The documentation for 'NetworkServerControl.logConnections(boolean)' states that Derby logs both connections and disconnections. As of 10.1.2.1 and (all) earlier releases, this is not true. The documentation should be corrected to avoid confusing users. The thought of adding logging of disconnections has also been posted on derby-dev. Byran Pendleton identified the following documentation with the incorrect description: http://db.apache.org/derby/javadoc/publishedapi/org/apache/derby/drda/NetworkServerControl.html http://db.apache.org/derby/docs/10.1/adminguide/radminconfigdb2jdrdalogconnections.html http://db.apache.org/derby/docs/10.0/manuals/admin/hubprnt23.html http://db.apache.org/derby/docs/10.1/adminguide/tadminlogfile.html Should we fix this in 10.0? If yes, please update fix versions for this issue. -- 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-402) INTERSECT/EXCEPT/UNION operators don't agree with documented behavior.
[ http://issues.apache.org/jira/browse/DERBY-402?page=all ] Jeff Levitt updated DERBY-402: -- Attachment: (was: rrefselectexpression.html) INTERSECT/EXCEPT/UNION operators don't agree with documented behavior. -- Key: DERBY-402 URL: http://issues.apache.org/jira/browse/DERBY-402 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0, 10.0.2.2 Reporter: A B Fix For: 10.2.0.0 I noticed the following two differences between what the documentation (Reference Manual) says about UNION/INTERSECT/EXCEPT queries and what the actual Derby behavior is. I'm filing this issue as a single bug against Derby, but if it turns out later that this is really just a documentation issue, or that these are improvements instead of bugs, anyone should feel free to change the relevant fields in this issue... 1) -- p. 63 of the Reference Manual (PDF version): SelectExpression - Naming columns First paragraph in this section includes the following: When the SelectExpression appears in a UNION, INTERSECT, or EXCEPT operator, the names from the first SelectExpression are taken as the names for the columns in the result of the operation. But this doesn't appear to be true. Ex: ij select a from t1 union select b from t2; 1 // This 1 should be A, according to doc. --- 1 2 If this behavior is intentional, then an ORDER BY clause on a UNION/INTERSECT/EXCEPT result set can only reference the result columns by position (ex. would have to use order by 1 in the above query since order by a doesn't work (because the name of the result column isn't a)). Note that if both SelectExpressions have the same column name, then things work differently: ij select a from t1 union select b as a from t2; A // Now it's A instead of 1. --- 1 2 So what needs to be corrected here? The documentation or the code? 2) -- p. 133 of the Reference Manual: Dynamic Parameters - Where dynamic parameters are allowed Number 16 says a dynamic parameter is allowed to represent a column if it appears in a UNION, INTERSECT, or EXCEPT expression. But the two examples that it gives both fail: ij SELECT ? FROM t UNION SELECT 1 FROM t; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. ij VALUES 1 UNION VALUES ?; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. I also tried preparing these statements using JDBC, but they failed there with the same error.. -- 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-402) INTERSECT/EXCEPT/UNION operators don't agree with documented behavior.
[ http://issues.apache.org/jira/browse/DERBY-402?page=all ] Jeff Levitt updated DERBY-402: -- Attachment: (was: rrefsqlj1083019.html) INTERSECT/EXCEPT/UNION operators don't agree with documented behavior. -- Key: DERBY-402 URL: http://issues.apache.org/jira/browse/DERBY-402 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0, 10.0.2.2 Reporter: A B Fix For: 10.2.0.0 I noticed the following two differences between what the documentation (Reference Manual) says about UNION/INTERSECT/EXCEPT queries and what the actual Derby behavior is. I'm filing this issue as a single bug against Derby, but if it turns out later that this is really just a documentation issue, or that these are improvements instead of bugs, anyone should feel free to change the relevant fields in this issue... 1) -- p. 63 of the Reference Manual (PDF version): SelectExpression - Naming columns First paragraph in this section includes the following: When the SelectExpression appears in a UNION, INTERSECT, or EXCEPT operator, the names from the first SelectExpression are taken as the names for the columns in the result of the operation. But this doesn't appear to be true. Ex: ij select a from t1 union select b from t2; 1 // This 1 should be A, according to doc. --- 1 2 If this behavior is intentional, then an ORDER BY clause on a UNION/INTERSECT/EXCEPT result set can only reference the result columns by position (ex. would have to use order by 1 in the above query since order by a doesn't work (because the name of the result column isn't a)). Note that if both SelectExpressions have the same column name, then things work differently: ij select a from t1 union select b as a from t2; A // Now it's A instead of 1. --- 1 2 So what needs to be corrected here? The documentation or the code? 2) -- p. 133 of the Reference Manual: Dynamic Parameters - Where dynamic parameters are allowed Number 16 says a dynamic parameter is allowed to represent a column if it appears in a UNION, INTERSECT, or EXCEPT expression. But the two examples that it gives both fail: ij SELECT ? FROM t UNION SELECT 1 FROM t; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. ij VALUES 1 UNION VALUES ?; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. I also tried preparing these statements using JDBC, but they failed there with the same error.. -- 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-402) INTERSECT/EXCEPT/UNION operators don't agree with documented behavior.
[ http://issues.apache.org/jira/browse/DERBY-402?page=all ] Jeff Levitt updated DERBY-402: -- Attachment: (was: derby402.diff) INTERSECT/EXCEPT/UNION operators don't agree with documented behavior. -- Key: DERBY-402 URL: http://issues.apache.org/jira/browse/DERBY-402 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0, 10.0.2.2 Reporter: A B Fix For: 10.2.0.0 I noticed the following two differences between what the documentation (Reference Manual) says about UNION/INTERSECT/EXCEPT queries and what the actual Derby behavior is. I'm filing this issue as a single bug against Derby, but if it turns out later that this is really just a documentation issue, or that these are improvements instead of bugs, anyone should feel free to change the relevant fields in this issue... 1) -- p. 63 of the Reference Manual (PDF version): SelectExpression - Naming columns First paragraph in this section includes the following: When the SelectExpression appears in a UNION, INTERSECT, or EXCEPT operator, the names from the first SelectExpression are taken as the names for the columns in the result of the operation. But this doesn't appear to be true. Ex: ij select a from t1 union select b from t2; 1 // This 1 should be A, according to doc. --- 1 2 If this behavior is intentional, then an ORDER BY clause on a UNION/INTERSECT/EXCEPT result set can only reference the result columns by position (ex. would have to use order by 1 in the above query since order by a doesn't work (because the name of the result column isn't a)). Note that if both SelectExpressions have the same column name, then things work differently: ij select a from t1 union select b as a from t2; A // Now it's A instead of 1. --- 1 2 So what needs to be corrected here? The documentation or the code? 2) -- p. 133 of the Reference Manual: Dynamic Parameters - Where dynamic parameters are allowed Number 16 says a dynamic parameter is allowed to represent a column if it appears in a UNION, INTERSECT, or EXCEPT expression. But the two examples that it gives both fail: ij SELECT ? FROM t UNION SELECT 1 FROM t; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. ij VALUES 1 UNION VALUES ?; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. I also tried preparing these statements using JDBC, but they failed there with the same error.. -- 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-402) INTERSECT/EXCEPT/UNION operators don't agree with documented behavior.
[ http://issues.apache.org/jira/browse/DERBY-402?page=all ] Jeff Levitt updated DERBY-402: -- Attachment: derby402Final.diff rrefselectexpression.html rrefsqlj1083019.html This patch needed to be updated since Eric Radzinski recently contributed a patch that modified one of the files in this patch. As a result, this patch would have caused a conflict, so I deleted the old patch and am replacing it with a new one with the same changes except it was made at a higher revision number. HTML files included for review. INTERSECT/EXCEPT/UNION operators don't agree with documented behavior. -- Key: DERBY-402 URL: http://issues.apache.org/jira/browse/DERBY-402 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0, 10.0.2.2 Reporter: A B Fix For: 10.2.0.0 Attachments: derby402Final.diff, rrefselectexpression.html, rrefsqlj1083019.html I noticed the following two differences between what the documentation (Reference Manual) says about UNION/INTERSECT/EXCEPT queries and what the actual Derby behavior is. I'm filing this issue as a single bug against Derby, but if it turns out later that this is really just a documentation issue, or that these are improvements instead of bugs, anyone should feel free to change the relevant fields in this issue... 1) -- p. 63 of the Reference Manual (PDF version): SelectExpression - Naming columns First paragraph in this section includes the following: When the SelectExpression appears in a UNION, INTERSECT, or EXCEPT operator, the names from the first SelectExpression are taken as the names for the columns in the result of the operation. But this doesn't appear to be true. Ex: ij select a from t1 union select b from t2; 1 // This 1 should be A, according to doc. --- 1 2 If this behavior is intentional, then an ORDER BY clause on a UNION/INTERSECT/EXCEPT result set can only reference the result columns by position (ex. would have to use order by 1 in the above query since order by a doesn't work (because the name of the result column isn't a)). Note that if both SelectExpressions have the same column name, then things work differently: ij select a from t1 union select b as a from t2; A // Now it's A instead of 1. --- 1 2 So what needs to be corrected here? The documentation or the code? 2) -- p. 133 of the Reference Manual: Dynamic Parameters - Where dynamic parameters are allowed Number 16 says a dynamic parameter is allowed to represent a column if it appears in a UNION, INTERSECT, or EXCEPT expression. But the two examples that it gives both fail: ij SELECT ? FROM t UNION SELECT 1 FROM t; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. ij VALUES 1 UNION VALUES ?; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. I also tried preparing these statements using JDBC, but they failed there with the same error.. -- 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-748) Should document the default schemas in a newly created database
[ http://issues.apache.org/jira/browse/DERBY-748?page=comments#action_12366932 ] Jeff Levitt commented on DERBY-748: --- If someone can provide me with the columns for these tables as well as other metadata such as those doc'd in the reference manuals for other tables (for example): http://db.apache.org/derby/docs/dev/ref/rrefsistabs28114.html If I get that kind of information I would be happy to place it in similar topics within the reference manual. Should document the default schemas in a newly created database --- Key: DERBY-748 URL: http://issues.apache.org/jira/browse/DERBY-748 Project: Derby Type: Improvement Components: Documentation Versions: 10.1.2.1 Reporter: Oyvind Bakksjo A newly created database will contain the following schemas: NULLID SQLJ SYS SYSCAT SYSCS_DIAG SYSCS_UTIL SYSFUN SYSIBM SYSPROC SYSSTAT These should be documented, at least in the Reference Guide. -- 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-936) Main branch docs display version as 10.1, should be 10.2.
[ http://issues.apache.org/jira/browse/DERBY-936?page=all ] Jeff Levitt updated DERBY-936: -- Attachment: derby936.diff This patch is a simple search and replace of Version 10.1 in the docs and replacesit with 10.2. Subsequent output html and PDF's will have version 10.2 displayed. Main branch docs display version as 10.1, should be 10.2. - Key: DERBY-936 URL: http://issues.apache.org/jira/browse/DERBY-936 Project: Derby Type: Improvement Components: Documentation Versions: 10.0.2.0 Reporter: Andrew McIntyre Attachments: derby936.diff Currently the output for the PDF and HTML Book formats of the manuals on the main branch display the version 10.1. Documentation changes have been committed which make the main branch of the documentation no longer proper for 10.1, so the version the main branch of the documentation displays should be 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-936) Main branch docs display version as 10.1, should be 10.2.
[ http://issues.apache.org/jira/browse/DERBY-936?page=all ] Jeff Levitt updated DERBY-936: -- Other Info: [Patch available] Main branch docs display version as 10.1, should be 10.2. - Key: DERBY-936 URL: http://issues.apache.org/jira/browse/DERBY-936 Project: Derby Type: Improvement Components: Documentation Versions: 10.0.2.0 Reporter: Andrew McIntyre Attachments: derby936.diff Currently the output for the PDF and HTML Book formats of the manuals on the main branch display the version 10.1. Documentation changes have been committed which make the main branch of the documentation no longer proper for 10.1, so the version the main branch of the documentation displays should be 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-629) Update documentation with correct default values for network server properties
[ http://issues.apache.org/jira/browse/DERBY-629?page=all ] Jeff Levitt updated DERBY-629: -- Attachment: derby629.diff radmindrdamaxthreads.html radmindrdaminthreads.html Thispatch changes the indicated default values to 0. HTML included for review... Update documentation with correct default values for network server properties -- Key: DERBY-629 URL: http://issues.apache.org/jira/browse/DERBY-629 Project: Derby Type: Sub-task Components: Documentation Versions: 10.2.0.0 Reporter: Deepa Remesh Priority: Minor Attachments: derby629.diff, radmindrdamaxthreads.html, radmindrdaminthreads.html Derby Server and Admin guide needs to be updated with the correct default value for the following network server properties: derby.drda.maxThreads derby.drda.minThreads derby.drda.timeSlice The default value for the above properties is 0. This information has to be updated in section 'Setting Network Server properties', pg 28 -29 -- 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-629) Update documentation with correct default values for network server properties
[ http://issues.apache.org/jira/browse/DERBY-629?page=all ] Jeff Levitt updated DERBY-629: -- Attachment: radmindrdatimeslice.html Update documentation with correct default values for network server properties -- Key: DERBY-629 URL: http://issues.apache.org/jira/browse/DERBY-629 Project: Derby Type: Sub-task Components: Documentation Versions: 10.2.0.0 Reporter: Deepa Remesh Priority: Minor Attachments: derby629.diff, radmindrdamaxthreads.html, radmindrdaminthreads.html, radmindrdatimeslice.html Derby Server and Admin guide needs to be updated with the correct default value for the following network server properties: derby.drda.maxThreads derby.drda.minThreads derby.drda.timeSlice The default value for the above properties is 0. This information has to be updated in section 'Setting Network Server properties', pg 28 -29 -- 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-629) Update documentation with correct default values for network server properties
[ http://issues.apache.org/jira/browse/DERBY-629?page=all ] Jeff Levitt updated DERBY-629: -- Other Info: [Patch available] Update documentation with correct default values for network server properties -- Key: DERBY-629 URL: http://issues.apache.org/jira/browse/DERBY-629 Project: Derby Type: Sub-task Components: Documentation Versions: 10.2.0.0 Reporter: Deepa Remesh Priority: Minor Attachments: derby629.diff, radmindrdamaxthreads.html, radmindrdaminthreads.html, radmindrdatimeslice.html Derby Server and Admin guide needs to be updated with the correct default value for the following network server properties: derby.drda.maxThreads derby.drda.minThreads derby.drda.timeSlice The default value for the above properties is 0. This information has to be updated in section 'Setting Network Server properties', pg 28 -29 -- 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-627) Documentation needs to be updated with correct return type for COUNT functions
[ http://issues.apache.org/jira/browse/DERBY-627?page=all ] Jeff Levitt updated DERBY-627: -- Attachment: derby627.diff rrefsqlj38716.html rrefsqlj66113.html Attached patch changes the indicated datatype to INTEGER in both files. HTML output included for review. Documentation needs to be updated with correct return type for COUNT functions -- Key: DERBY-627 URL: http://issues.apache.org/jira/browse/DERBY-627 Project: Derby Type: Bug Components: Documentation Versions: 10.2.0.0 Reporter: Deepa Remesh Priority: Minor Attachments: derby627.diff, rrefsqlj38716.html, rrefsqlj66113.html Derby Reference manual (Section 'Built-in functions', pg80-81) specifies the resulting data type of COUNT and COUNT(*) functions as BIGINT. Whereas, Derby returns INTEGER type for these functions. -- 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-627) Documentation needs to be updated with correct return type for COUNT functions
[ http://issues.apache.org/jira/browse/DERBY-627?page=all ] Jeff Levitt updated DERBY-627: -- Other Info: [Patch available] Documentation needs to be updated with correct return type for COUNT functions -- Key: DERBY-627 URL: http://issues.apache.org/jira/browse/DERBY-627 Project: Derby Type: Bug Components: Documentation Versions: 10.2.0.0 Reporter: Deepa Remesh Priority: Minor Attachments: derby627.diff, rrefsqlj38716.html, rrefsqlj66113.html Derby Reference manual (Section 'Built-in functions', pg80-81) specifies the resulting data type of COUNT and COUNT(*) functions as BIGINT. Whereas, Derby returns INTEGER type for these functions. -- 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-542) Update documentation for DERBY-470
[ http://issues.apache.org/jira/browse/DERBY-542?page=all ] Jeff Levitt updated DERBY-542: -- Attachment: derby542.diff rtoolsijcomref88554.html Attached patch adds the note to the topic as requested. HTML output included for review. Update documentation for DERBY-470 -- Key: DERBY-542 URL: http://issues.apache.org/jira/browse/DERBY-542 Project: Derby Type: Sub-task Components: Documentation Versions: 10.1.1.0, 10.2.0.0 Reporter: Deepa Remesh Priority: Minor Attachments: derby542.diff, rtoolsijcomref88554.html To reflect the change for DERBY-470, the following information has to be added to Derby Tools and Utilities Guide: Section ij commands and errors reference--LocalizedDisplay: NUMERIC and DECIMAL values are not localized on J2ME/CDC/Foundation Profile because of platform limitations. Please review this. Also, is there any other place in the documents where this info needs to be added? It would be great if someone working on documents can make this change. -- 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-542) Update documentation for DERBY-470
[ http://issues.apache.org/jira/browse/DERBY-542?page=all ] Jeff Levitt updated DERBY-542: -- Other Info: [Patch available] Update documentation for DERBY-470 -- Key: DERBY-542 URL: http://issues.apache.org/jira/browse/DERBY-542 Project: Derby Type: Sub-task Components: Documentation Versions: 10.1.1.0, 10.2.0.0 Reporter: Deepa Remesh Priority: Minor Attachments: derby542.diff, rtoolsijcomref88554.html To reflect the change for DERBY-470, the following information has to be added to Derby Tools and Utilities Guide: Section ij commands and errors reference--LocalizedDisplay: NUMERIC and DECIMAL values are not localized on J2ME/CDC/Foundation Profile because of platform limitations. Please review this. Also, is there any other place in the documents where this info needs to be added? It would be great if someone working on documents can make this change. -- 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-539) Update the Create Index statement in the Derby documentation with additional information
[ http://issues.apache.org/jira/browse/DERBY-539?page=all ] Jeff Levitt updated DERBY-539: -- Attachment: derby539.diff rrefsqlj20937.html Attached patch adds the sentences and modifies the existing text as requested. Please review the included HTML files to approve the commit. Thanks! Update the Create Index statement in the Derby documentation with additional information Key: DERBY-539 URL: http://issues.apache.org/jira/browse/DERBY-539 Project: Derby Type: Improvement Components: Documentation Reporter: Susan Cline Priority: Minor Attachments: derby539.diff, rrefsqlj20937.html In the 'Create Index' statement documentation of the 10.1 Reference Guide (derby/docs/10.1/ref/rrefsqlj20937.html) this statement is made about creating indexes and constraints: Indexes and constraints Unique, primary key, and foreign key constraints generate indexes that enforce or back the constraint (and are thus sometimes called backing indexes). If a column or set of columns has a UNIQUE or PRIMARY KEY constraint on it, you can not create an index on those columns. Derby has already created it for you with a system-generated name. This is true, but I think it can be expanded upon to be clearer. A suggestion for this is below: Indexes and constraints Unique, primary key, and foreign key constraints generate indexes that enforce or back the constraint (and are thus sometimes called backing indexes). If a column or set of columns has a PRIMARY KEY constraint on it, you can not create an index on those columns. If a column or set of columns has a UNIQUE constraint on it, you can not create an index on those columns, but you can create a PRIMARY KEY constraint on it. Addtionally, if this is the case, a backing index will be created for the PRIMARY KEY constraint so two indexes will now exist on the column or set of columns that had the UNIQUE constraint on it. This issue came up when I noticed that I could create a unique index on a column, then create a PK on that column. When I used a tool to generate DDL for the table I noticed one constraint and two indexes on the column which didn't make sense at first when reading the existing documentation. With the additional information above I think it explains the real behaviour better. -- 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-539) Update the Create Index statement in the Derby documentation with additional information
[ http://issues.apache.org/jira/browse/DERBY-539?page=all ] Jeff Levitt updated DERBY-539: -- Other Info: [Patch available] Update the Create Index statement in the Derby documentation with additional information Key: DERBY-539 URL: http://issues.apache.org/jira/browse/DERBY-539 Project: Derby Type: Improvement Components: Documentation Reporter: Susan Cline Priority: Minor Attachments: derby539.diff, rrefsqlj20937.html In the 'Create Index' statement documentation of the 10.1 Reference Guide (derby/docs/10.1/ref/rrefsqlj20937.html) this statement is made about creating indexes and constraints: Indexes and constraints Unique, primary key, and foreign key constraints generate indexes that enforce or back the constraint (and are thus sometimes called backing indexes). If a column or set of columns has a UNIQUE or PRIMARY KEY constraint on it, you can not create an index on those columns. Derby has already created it for you with a system-generated name. This is true, but I think it can be expanded upon to be clearer. A suggestion for this is below: Indexes and constraints Unique, primary key, and foreign key constraints generate indexes that enforce or back the constraint (and are thus sometimes called backing indexes). If a column or set of columns has a PRIMARY KEY constraint on it, you can not create an index on those columns. If a column or set of columns has a UNIQUE constraint on it, you can not create an index on those columns, but you can create a PRIMARY KEY constraint on it. Addtionally, if this is the case, a backing index will be created for the PRIMARY KEY constraint so two indexes will now exist on the column or set of columns that had the UNIQUE constraint on it. This issue came up when I noticed that I could create a unique index on a column, then create a PK on that column. When I used a tool to generate DDL for the table I noticed one constraint and two indexes on the column which didn't make sense at first when reading the existing documentation. With the additional information above I think it explains the real behaviour better. -- 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-402) INTERSECT/EXCEPT/UNION operators don't agree with documented behavior.
[ http://issues.apache.org/jira/browse/DERBY-402?page=comments#action_12366845 ] Jeff Levitt commented on DERBY-402: --- So I'm trying to understand the doc impact of this bug. Should the offending sentences just be removed? Thanks! INTERSECT/EXCEPT/UNION operators don't agree with documented behavior. -- Key: DERBY-402 URL: http://issues.apache.org/jira/browse/DERBY-402 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0, 10.0.2.2 Reporter: A B Fix For: 10.2.0.0 I noticed the following two differences between what the documentation (Reference Manual) says about UNION/INTERSECT/EXCEPT queries and what the actual Derby behavior is. I'm filing this issue as a single bug against Derby, but if it turns out later that this is really just a documentation issue, or that these are improvements instead of bugs, anyone should feel free to change the relevant fields in this issue... 1) -- p. 63 of the Reference Manual (PDF version): SelectExpression - Naming columns First paragraph in this section includes the following: When the SelectExpression appears in a UNION, INTERSECT, or EXCEPT operator, the names from the first SelectExpression are taken as the names for the columns in the result of the operation. But this doesn't appear to be true. Ex: ij select a from t1 union select b from t2; 1 // This 1 should be A, according to doc. --- 1 2 If this behavior is intentional, then an ORDER BY clause on a UNION/INTERSECT/EXCEPT result set can only reference the result columns by position (ex. would have to use order by 1 in the above query since order by a doesn't work (because the name of the result column isn't a)). Note that if both SelectExpressions have the same column name, then things work differently: ij select a from t1 union select b as a from t2; A // Now it's A instead of 1. --- 1 2 So what needs to be corrected here? The documentation or the code? 2) -- p. 133 of the Reference Manual: Dynamic Parameters - Where dynamic parameters are allowed Number 16 says a dynamic parameter is allowed to represent a column if it appears in a UNION, INTERSECT, or EXCEPT expression. But the two examples that it gives both fail: ij SELECT ? FROM t UNION SELECT 1 FROM t; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. ij VALUES 1 UNION VALUES ?; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. I also tried preparing these statements using JDBC, but they failed there with the same error.. -- 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-402) INTERSECT/EXCEPT/UNION operators don't agree with documented behavior.
[ http://issues.apache.org/jira/browse/DERBY-402?page=all ] Jeff Levitt updated DERBY-402: -- Other Info: [Patch available] INTERSECT/EXCEPT/UNION operators don't agree with documented behavior. -- Key: DERBY-402 URL: http://issues.apache.org/jira/browse/DERBY-402 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0, 10.0.2.2 Reporter: A B Fix For: 10.2.0.0 Attachments: derby402.diff, rrefselectexpression.html, rrefsqlj1083019.html I noticed the following two differences between what the documentation (Reference Manual) says about UNION/INTERSECT/EXCEPT queries and what the actual Derby behavior is. I'm filing this issue as a single bug against Derby, but if it turns out later that this is really just a documentation issue, or that these are improvements instead of bugs, anyone should feel free to change the relevant fields in this issue... 1) -- p. 63 of the Reference Manual (PDF version): SelectExpression - Naming columns First paragraph in this section includes the following: When the SelectExpression appears in a UNION, INTERSECT, or EXCEPT operator, the names from the first SelectExpression are taken as the names for the columns in the result of the operation. But this doesn't appear to be true. Ex: ij select a from t1 union select b from t2; 1 // This 1 should be A, according to doc. --- 1 2 If this behavior is intentional, then an ORDER BY clause on a UNION/INTERSECT/EXCEPT result set can only reference the result columns by position (ex. would have to use order by 1 in the above query since order by a doesn't work (because the name of the result column isn't a)). Note that if both SelectExpressions have the same column name, then things work differently: ij select a from t1 union select b as a from t2; A // Now it's A instead of 1. --- 1 2 So what needs to be corrected here? The documentation or the code? 2) -- p. 133 of the Reference Manual: Dynamic Parameters - Where dynamic parameters are allowed Number 16 says a dynamic parameter is allowed to represent a column if it appears in a UNION, INTERSECT, or EXCEPT expression. But the two examples that it gives both fail: ij SELECT ? FROM t UNION SELECT 1 FROM t; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. ij VALUES 1 UNION VALUES ?; ERROR 42X34: There is a ? parameter in the select list. This is not allowed. I also tried preparing these statements using JDBC, but they failed there with the same error.. -- 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-994) SQL examples for LEFT OUTER JOIN and RIGHT OUTER JOIN in the Derby Reference manual are incorrect
[ http://issues.apache.org/jira/browse/DERBY-994?page=all ] Jeff Levitt updated DERBY-994: -- Other Info: [Patch available] SQL examples for LEFT OUTER JOIN and RIGHT OUTER JOIN in the Derby Reference manual are incorrect - Key: DERBY-994 URL: http://issues.apache.org/jira/browse/DERBY-994 Project: Derby Type: Bug Components: Documentation Versions: 10.0.2.0 Reporter: Rajesh Kartha Fix For: 10.2.0.0 Attachments: derby994.diff, rrefsqlj18922.html, rrefsqlj57522.html The SQL examples for the following in the reference manual are wrong: - LEFT OUTER JOIN - RIGHT OUTER JOIN The incorrectness are pointed out below. Also the fix (correct sql and descriptions) that should replace these are provided. Can someone please review this and commit into the codeline. LEFT OUTER JOIN : (v10.1) http://db.apache.org/derby/docs/10.1/ref/rrefsqlj18922.html (trunk) http://db.apache.org/derby/docs/dev/ref/rrefsqlj18922.html The manual shows: quote --match cities to countries [wrong description: should mention cities to countries in Asia] == SELECT CITIES.COUNTRY, REGION FROM Countries LEFT OUTER JOIN Cities ON CITY_ID=CITY_ID WHERE REGION = 'Asia'; [wrong sql: This will return 1305 rows meaningless rows] == -- use the synonymous syntax, RIGHT JOIN, to achieve exactly -- the same results as in the example above [wrong description: The synonymous syntax is LEFT JOIN] == SELECT COUNTRIES.COUNTRY, REGION FROM Countries LEFT JOIN Cities ON CITY_ID=CITY_ID; [wrong sql: Returns a Cartesian product of the two tables: 9918 rows selected] == /quote The correct description and sql for LEFT OUTER JOIN should be: --- --match cities to countries in Asia SELECT COUNTRIES.COUNTRY, CITIES.CITY_NAME,REGION FROM COUNTRIES LEFT OUTER JOIN CITIES ON CITIES.COUNTRY_ISO_CODE = COUNTRIES.COUNTRY_ISO_CODE WHERE REGION='Asia'; -- use the synonymous syntax, LEFT JOIN, to achieve exactly -- the same results as in the example above SELECT COUNTRIES.COUNTRY, CITIES.CITY_NAME,REGION FROM COUNTRIES LEFT JOIN CITIES ON CITIES.COUNTRY_ISO_CODE = COUNTRIES.COUNTRY_ISO_CODE WHERE REGION='Asia'; [Both the above queries will return COUNTRY |CITY_NAME |REGION -- Afghanistan |Kabul |Asia Bangladesh|NULL|Asia Cambodia |NULL|Asia China |Hong Kong |Asia China |Shanghai|Asia India |Bombay |Asia India |Calcutta|Asia Indonesia |Jakarta |Asia Japan |Osaka |Asia Japan |Tokyo |Asia Korea, Republic of|Seoul |Asia Malaysia |NULL|Asia Nepal |NULL|Asia Philippines |Manila |Asia Singapore |Singapore |Asia Sri Lanka |NULL|Asia Thailand |NULL|Asia Viet Nam |NULL|Asia 18 rows selected] == RIGHT OUTER JOIN: = (v10.1) http://db.apache.org/derby/docs/10.1/ref/rrefsqlj57522.html (trunk) http://db.apache.org/derby/docs/dev/ref/rrefsqlj57522.html The manual shows: quote -- get all countries and corresponding cities, including -- countries without any cities SELECT CITY_NAME, CITIES.COUNTRY FROM CITIES RIGHT OUTER JOIN COUNTRIES ON CITIES.COUNTRY_ISO_CODE = COUNTRIES.COUNTRY_ISO_CODE; [wrong sql: Return meaningless 156 rows ] == -- get all countries in Africa and corresponding cities, including -- countries without any cities SELECT CITY_NAME, CITIES.COUNTRY FROM CITIES RIGHT OUTER JOIN COUNTRIES ON CITIES.COUNTRY_ISO_CODE = COUNTRIES.COUNTRY_ISO_CODE; WHERE Countries.region = 'frica'; [wrong sql: 1) 'frica' is incorrect in the WHERE clause 2) incorrect results with NULL country values 3) incorrect ';' before WHERE clause] == -- use the synonymous syntax, RIGHT JOIN, to achieve exactly -- the same results as in the example above SELECT CITY_NAME, CITIES.COUNTRY FROM CITIES RIGHT JOIN COUNTRIES ON CITIES.COUNTRY_ISO_CODE = COUNTRIES.COUNTRY_ISO_CODE WHERE Countries.region = 'Africa'; [wrong sql: Incorrect results with NULL country values] == /quote The correct description and sql for RIGHT OUTER JOIN should be:
[jira] Updated: (DERBY-482) GENERATED BY DEFAULT option should be documented in Derby Tools and Utilities guide under Importing into tables with identity columns section.
[ http://issues.apache.org/jira/browse/DERBY-482?page=all ] Jeff Levitt updated DERBY-482: -- Attachment: derby482.diff ctoolsimportidentitycol.html For this patch, I copied the information in the Reference Manual on GENERATED BY DEFAULT and placed it in the Importing into tables with identity columns topic in the Tools and Utilities Guide after the information on GENERATED ALWAYS. I then modified the introductory paragraph of the topic to mention both options. I am including an HTML output file for review with this patch. I'd appreciate any feedback. Thanks! GENERATED BY DEFAULT option should be documented in Derby Tools and Utilities guide under Importing into tables with identity columns section. Key: DERBY-482 URL: http://issues.apache.org/jira/browse/DERBY-482 Project: Derby Type: Improvement Components: Documentation Versions: 10.1.1.0 Reporter: Mamta A. Satoor Attachments: ctoolsimportidentitycol.html, derby482.diff Tomohito added support for import into identity columns by adding GENERATED BY DEFAULT option. This is documented in the Reference Guide but not in the Tools and Utilites Guide which is where a user would look for details on import. IMHO, there should be information about this in Importing into tables with identity columns section in Tools and Utilities Guide. -- 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-482) GENERATED BY DEFAULT option should be documented in Derby Tools and Utilities guide under Importing into tables with identity columns section.
[ http://issues.apache.org/jira/browse/DERBY-482?page=all ] Jeff Levitt updated DERBY-482: -- Other Info: [Patch available] GENERATED BY DEFAULT option should be documented in Derby Tools and Utilities guide under Importing into tables with identity columns section. Key: DERBY-482 URL: http://issues.apache.org/jira/browse/DERBY-482 Project: Derby Type: Improvement Components: Documentation Versions: 10.1.1.0 Reporter: Mamta A. Satoor Attachments: ctoolsimportidentitycol.html, derby482.diff Tomohito added support for import into identity columns by adding GENERATED BY DEFAULT option. This is documented in the Reference Guide but not in the Tools and Utilites Guide which is where a user would look for details on import. IMHO, there should be information about this in Importing into tables with identity columns section in Tools and Utilities Guide. -- 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-994) SQL examples for LEFT OUTER JOIN and RIGHT OUTER JOIN in the Derby Reference manual are incorrect
[ http://issues.apache.org/jira/browse/DERBY-994?page=all ] Jeff Levitt updated DERBY-994: -- Attachment: derby994.diff rrefsqlj18922.html rrefsqlj57522.html Attached patch fixes the examples as requested. HTML output included for review. SQL examples for LEFT OUTER JOIN and RIGHT OUTER JOIN in the Derby Reference manual are incorrect - Key: DERBY-994 URL: http://issues.apache.org/jira/browse/DERBY-994 Project: Derby Type: Bug Components: Documentation Versions: 10.0.2.0 Reporter: Rajesh Kartha Fix For: 10.2.0.0 Attachments: derby994.diff, rrefsqlj18922.html, rrefsqlj57522.html The SQL examples for the following in the reference manual are wrong: - LEFT OUTER JOIN - RIGHT OUTER JOIN The incorrectness are pointed out below. Also the fix (correct sql and descriptions) that should replace these are provided. Can someone please review this and commit into the codeline. LEFT OUTER JOIN : (v10.1) http://db.apache.org/derby/docs/10.1/ref/rrefsqlj18922.html (trunk) http://db.apache.org/derby/docs/dev/ref/rrefsqlj18922.html The manual shows: quote --match cities to countries [wrong description: should mention cities to countries in Asia] == SELECT CITIES.COUNTRY, REGION FROM Countries LEFT OUTER JOIN Cities ON CITY_ID=CITY_ID WHERE REGION = 'Asia'; [wrong sql: This will return 1305 rows meaningless rows] == -- use the synonymous syntax, RIGHT JOIN, to achieve exactly -- the same results as in the example above [wrong description: The synonymous syntax is LEFT JOIN] == SELECT COUNTRIES.COUNTRY, REGION FROM Countries LEFT JOIN Cities ON CITY_ID=CITY_ID; [wrong sql: Returns a Cartesian product of the two tables: 9918 rows selected] == /quote The correct description and sql for LEFT OUTER JOIN should be: --- --match cities to countries in Asia SELECT COUNTRIES.COUNTRY, CITIES.CITY_NAME,REGION FROM COUNTRIES LEFT OUTER JOIN CITIES ON CITIES.COUNTRY_ISO_CODE = COUNTRIES.COUNTRY_ISO_CODE WHERE REGION='Asia'; -- use the synonymous syntax, LEFT JOIN, to achieve exactly -- the same results as in the example above SELECT COUNTRIES.COUNTRY, CITIES.CITY_NAME,REGION FROM COUNTRIES LEFT JOIN CITIES ON CITIES.COUNTRY_ISO_CODE = COUNTRIES.COUNTRY_ISO_CODE WHERE REGION='Asia'; [Both the above queries will return COUNTRY |CITY_NAME |REGION -- Afghanistan |Kabul |Asia Bangladesh|NULL|Asia Cambodia |NULL|Asia China |Hong Kong |Asia China |Shanghai|Asia India |Bombay |Asia India |Calcutta|Asia Indonesia |Jakarta |Asia Japan |Osaka |Asia Japan |Tokyo |Asia Korea, Republic of|Seoul |Asia Malaysia |NULL|Asia Nepal |NULL|Asia Philippines |Manila |Asia Singapore |Singapore |Asia Sri Lanka |NULL|Asia Thailand |NULL|Asia Viet Nam |NULL|Asia 18 rows selected] == RIGHT OUTER JOIN: = (v10.1) http://db.apache.org/derby/docs/10.1/ref/rrefsqlj57522.html (trunk) http://db.apache.org/derby/docs/dev/ref/rrefsqlj57522.html The manual shows: quote -- get all countries and corresponding cities, including -- countries without any cities SELECT CITY_NAME, CITIES.COUNTRY FROM CITIES RIGHT OUTER JOIN COUNTRIES ON CITIES.COUNTRY_ISO_CODE = COUNTRIES.COUNTRY_ISO_CODE; [wrong sql: Return meaningless 156 rows ] == -- get all countries in Africa and corresponding cities, including -- countries without any cities SELECT CITY_NAME, CITIES.COUNTRY FROM CITIES RIGHT OUTER JOIN COUNTRIES ON CITIES.COUNTRY_ISO_CODE = COUNTRIES.COUNTRY_ISO_CODE; WHERE Countries.region = 'frica'; [wrong sql: 1) 'frica' is incorrect in the WHERE clause 2) incorrect results with NULL country values 3) incorrect ';' before WHERE clause] == -- use the synonymous syntax, RIGHT JOIN, to achieve exactly -- the same results as in the example above SELECT CITY_NAME, CITIES.COUNTRY FROM CITIES RIGHT JOIN COUNTRIES ON CITIES.COUNTRY_ISO_CODE = COUNTRIES.COUNTRY_ISO_CODE WHERE Countries.region = 'Africa';
[jira] Commented: (DERBY-486) Fix Error message X0X07 in doc to match string changes in code
[ http://issues.apache.org/jira/browse/DERBY-486?page=comments#action_12362914 ] Jeff Levitt commented on DERBY-486: --- The patch looks good to me; the changes bring the error message text in the doc in line with the code change. I recommend a commit. Thanks! Fix Error message X0X07 in doc to match string changes in code -- Key: DERBY-486 URL: http://issues.apache.org/jira/browse/DERBY-486 Project: Derby Type: Sub-task Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 Attachments: DERBY-486.patch This is a subtask of DERBY-483 to match the string changes in the documentation. -- 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-391) Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password
[ http://issues.apache.org/jira/browse/DERBY-391?page=all ] Jeff Levitt updated DERBY-391: -- Attachment: (was: rtoolsijproprefpassword.html) Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password --- Key: DERBY-391 URL: http://issues.apache.org/jira/browse/DERBY-391 Project: Derby Type: Improvement Components: Documentation Versions: 10.1.1.0 Reporter: Myrna van Lunteren Priority: Minor Fix For: 10.2.0.0 The Tools and Utilities guide documents the ij properties. However, it does not have any documentation about the following properties ij.datasource ij.password ij.user I suggest something like this (but someone else should review): ij.dataSource Function This property allows one to specify the datasource that should be used to access the database. When specifying a datasource, Derby does *not* use the DriverManager mechanism to establish connections. For more information about DataSources, refer to the JDBC documentation and to the Derby Developer's Guide, section Using Derby as a J2EE Resource Manager. To establish a connection using ij.dataSource, you need to use additional ij.dataSource properties to set some additional properties: ij.dataSource.databaseName ij.dataSource.createDatabase Syntax ij.dataSource=datasourcename ij.dataSource.databaseName=databaseName [ij.dataSource.createDatabase=create] Example java -Dij.dataSource=org.apache.derby.jdbc.EmbeddedDataSource -Dij.dataSource.databaseName=toursDB -Dij.dataSource.createDatabase=create ij.password Function Specifies the password used to make connections with. When you connect like this, and ij creates the database, you will allways need to know that password in order to access the database, unless you set up additional users. For more information about authentication see the Derby Developer's Guide. Syntax ij.pasword=password Example java -Dij.user=me -Dij.password=mine org.apache.derby.tools.ij See also ij.user; Derby Developer's Guide - Derby and Security ij.user Function Specifies the user with which connections are made by default. When you connect like this, ij assumes that the database schema to be used is the same as the username provided. However, certain database objects cannot be created until a schema exists, i.e. until a create schema name has been issued, followed by a set schema name, or fully qualifying the database objects to be created. If no user is specified, no set schema has been issued, or create statements do not qualify the schema, all database objects are assumed to be under schema 'APP'. Syntax ij.user=username Example java -Dij.user=me -Dij.password=mine org.apache.derby.tools.ij ij version 10.1 ij set schema finance; ij select * from accounts; ij.password; Derby Developer's Guide - Derby and Security -- 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-391) Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password
[ http://issues.apache.org/jira/browse/DERBY-391?page=all ] Jeff Levitt updated DERBY-391: -- Attachment: (was: rtoolsijproprefuser.html) Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password --- Key: DERBY-391 URL: http://issues.apache.org/jira/browse/DERBY-391 Project: Derby Type: Improvement Components: Documentation Versions: 10.1.1.0 Reporter: Myrna van Lunteren Priority: Minor Fix For: 10.2.0.0 The Tools and Utilities guide documents the ij properties. However, it does not have any documentation about the following properties ij.datasource ij.password ij.user I suggest something like this (but someone else should review): ij.dataSource Function This property allows one to specify the datasource that should be used to access the database. When specifying a datasource, Derby does *not* use the DriverManager mechanism to establish connections. For more information about DataSources, refer to the JDBC documentation and to the Derby Developer's Guide, section Using Derby as a J2EE Resource Manager. To establish a connection using ij.dataSource, you need to use additional ij.dataSource properties to set some additional properties: ij.dataSource.databaseName ij.dataSource.createDatabase Syntax ij.dataSource=datasourcename ij.dataSource.databaseName=databaseName [ij.dataSource.createDatabase=create] Example java -Dij.dataSource=org.apache.derby.jdbc.EmbeddedDataSource -Dij.dataSource.databaseName=toursDB -Dij.dataSource.createDatabase=create ij.password Function Specifies the password used to make connections with. When you connect like this, and ij creates the database, you will allways need to know that password in order to access the database, unless you set up additional users. For more information about authentication see the Derby Developer's Guide. Syntax ij.pasword=password Example java -Dij.user=me -Dij.password=mine org.apache.derby.tools.ij See also ij.user; Derby Developer's Guide - Derby and Security ij.user Function Specifies the user with which connections are made by default. When you connect like this, ij assumes that the database schema to be used is the same as the username provided. However, certain database objects cannot be created until a schema exists, i.e. until a create schema name has been issued, followed by a set schema name, or fully qualifying the database objects to be created. If no user is specified, no set schema has been issued, or create statements do not qualify the schema, all database objects are assumed to be under schema 'APP'. Syntax ij.user=username Example java -Dij.user=me -Dij.password=mine org.apache.derby.tools.ij ij version 10.1 ij set schema finance; ij select * from accounts; ij.password; Derby Developer's Guide - Derby and Security -- 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-391) Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password
[ http://issues.apache.org/jira/browse/DERBY-391?page=all ] Jeff Levitt updated DERBY-391: -- Attachment: derby391firsthalf.diff Here's the patch! Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password --- Key: DERBY-391 URL: http://issues.apache.org/jira/browse/DERBY-391 Project: Derby Type: Improvement Components: Documentation Versions: 10.1.1.0 Reporter: Myrna van Lunteren Priority: Minor Fix For: 10.2.0.0 Attachments: derby391firsthalf.diff, rtoolsijproprefdatasource.html, rtoolsijproprefpassword.html, rtoolsijproprefuser.html The Tools and Utilities guide documents the ij properties. However, it does not have any documentation about the following properties ij.datasource ij.password ij.user I suggest something like this (but someone else should review): ij.dataSource Function This property allows one to specify the datasource that should be used to access the database. When specifying a datasource, Derby does *not* use the DriverManager mechanism to establish connections. For more information about DataSources, refer to the JDBC documentation and to the Derby Developer's Guide, section Using Derby as a J2EE Resource Manager. To establish a connection using ij.dataSource, you need to use additional ij.dataSource properties to set some additional properties: ij.dataSource.databaseName ij.dataSource.createDatabase Syntax ij.dataSource=datasourcename ij.dataSource.databaseName=databaseName [ij.dataSource.createDatabase=create] Example java -Dij.dataSource=org.apache.derby.jdbc.EmbeddedDataSource -Dij.dataSource.databaseName=toursDB -Dij.dataSource.createDatabase=create ij.password Function Specifies the password used to make connections with. When you connect like this, and ij creates the database, you will allways need to know that password in order to access the database, unless you set up additional users. For more information about authentication see the Derby Developer's Guide. Syntax ij.pasword=password Example java -Dij.user=me -Dij.password=mine org.apache.derby.tools.ij See also ij.user; Derby Developer's Guide - Derby and Security ij.user Function Specifies the user with which connections are made by default. When you connect like this, ij assumes that the database schema to be used is the same as the username provided. However, certain database objects cannot be created until a schema exists, i.e. until a create schema name has been issued, followed by a set schema name, or fully qualifying the database objects to be created. If no user is specified, no set schema has been issued, or create statements do not qualify the schema, all database objects are assumed to be under schema 'APP'. Syntax ij.user=username Example java -Dij.user=me -Dij.password=mine org.apache.derby.tools.ij ij version 10.1 ij set schema finance; ij select * from accounts; ij.password; Derby Developer's Guide - Derby and Security -- 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-725) NULLIF and CASE expressions section in reference manual contains two stale paragraphs.
[ http://issues.apache.org/jira/browse/DERBY-725?page=all ] Jeff Levitt updated DERBY-725: -- Attachment: derby725.diff rrefcasenullif.html Attached patch removes the two paragraphs as requested. HTML output included for review... NULLIF and CASE expressions section in reference manual contains two stale paragraphs. -- Key: DERBY-725 URL: http://issues.apache.org/jira/browse/DERBY-725 Project: Derby Type: Bug Components: Documentation Versions: 10.1.2.1 Reporter: Daniel John Debrunner Priority: Trivial Attachments: derby725.diff, rrefcasenullif.html The two paragraphs below from 10.1 ref manual, page 78 in pdf can be removed. You do not need to use the CASE expression for avoiding NullPointerExceptions when a nullable column becomes a method receiver. If the value of the instance specified in an instance method invocation is null, the result of the invocation is null (SQL NULL). However, you still might need to use the CASE expression for when a nullable column is a primitive method parameter. -- 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-391) Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password
[ http://issues.apache.org/jira/browse/DERBY-391?page=all ] Jeff Levitt updated DERBY-391: -- Attachment: rtoolsijproprefdatasource.html rtoolsijproprefuser.html rtoolsijproprefpassword.html Attached is a patch for the original issue. The three html files are for review. Thanks! Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password --- Key: DERBY-391 URL: http://issues.apache.org/jira/browse/DERBY-391 Project: Derby Type: Improvement Components: Documentation Versions: 10.1.1.0 Reporter: Myrna van Lunteren Priority: Minor Fix For: 10.2.0.0 Attachments: rtoolsijproprefdatasource.html, rtoolsijproprefpassword.html, rtoolsijproprefuser.html The Tools and Utilities guide documents the ij properties. However, it does not have any documentation about the following properties ij.datasource ij.password ij.user I suggest something like this (but someone else should review): ij.dataSource Function This property allows one to specify the datasource that should be used to access the database. When specifying a datasource, Derby does *not* use the DriverManager mechanism to establish connections. For more information about DataSources, refer to the JDBC documentation and to the Derby Developer's Guide, section Using Derby as a J2EE Resource Manager. To establish a connection using ij.dataSource, you need to use additional ij.dataSource properties to set some additional properties: ij.dataSource.databaseName ij.dataSource.createDatabase Syntax ij.dataSource=datasourcename ij.dataSource.databaseName=databaseName [ij.dataSource.createDatabase=create] Example java -Dij.dataSource=org.apache.derby.jdbc.EmbeddedDataSource -Dij.dataSource.databaseName=toursDB -Dij.dataSource.createDatabase=create ij.password Function Specifies the password used to make connections with. When you connect like this, and ij creates the database, you will allways need to know that password in order to access the database, unless you set up additional users. For more information about authentication see the Derby Developer's Guide. Syntax ij.pasword=password Example java -Dij.user=me -Dij.password=mine org.apache.derby.tools.ij See also ij.user; Derby Developer's Guide - Derby and Security ij.user Function Specifies the user with which connections are made by default. When you connect like this, ij assumes that the database schema to be used is the same as the username provided. However, certain database objects cannot be created until a schema exists, i.e. until a create schema name has been issued, followed by a set schema name, or fully qualifying the database objects to be created. If no user is specified, no set schema has been issued, or create statements do not qualify the schema, all database objects are assumed to be under schema 'APP'. Syntax ij.user=username Example java -Dij.user=me -Dij.password=mine org.apache.derby.tools.ij ij version 10.1 ij set schema finance; ij select * from accounts; ij.password; Derby Developer's Guide - Derby and Security -- 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-687) Get DITA ASL distribution working for Derby docs
[ http://issues.apache.org/jira/browse/DERBY-687?page=all ] Jeff Levitt updated DERBY-687: -- Attachment: conductor.xml build.xml dita2fo-shell.xsl Here are my modifications for the 1.2.1 DITA-OT ASL license release, as described in: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200511.mbox/raw/[EMAIL PROTECTED] I made a few more tweaks since that note, so if anyone is using these, use the ones attached to this JIRA issue, not the ones attached to that note. However, links in PDF documents still dont seem to work under the new DITA-OT release. The PDF navigation bar links seem to work fine, but while my modifications do add names to the table of contents, they wont link to the pages they are on. In addition, links in the PDF's such as for more information, see xxx are also not linking, even though the linked xxx title is being pulled in fine, which is strange. I can't seem to find what has been changed between the release we use to build Derby docs and the recent Apache licensed release that causes these problems, but I do know they are not in my modified dita2fo-shell.xsl file. To verify, I replaced that file from the DITA-OT1.0.1 release that we use for the current Derby build with my modified 1.2.1 version in a local build and tested it. It works fine and all links work as well under the old setup. But some other file in the 1.2.1 ASL license version is changed, and we need to find out where in order to get those links working. Either way, the files I attached to this JIRA issue are ready for Andrew's mods so that we can have a Derby ant build using my mods, but after Andrew is done with that, we should investigate further to see what other mods are now needed to get the newly licensed files back to where we were with working links. Get DITA ASL distribution working for Derby docs Key: DERBY-687 URL: http://issues.apache.org/jira/browse/DERBY-687 Project: Derby Type: Improvement Components: Documentation Reporter: Jean T. Anderson Assignee: Andrew McIntyre Priority: Minor Attachments: build.xml, conductor.xml, dita2fo-shell.xsl The DITA instructions at http://db.apache.org/derby/manuals/dita.html say to use Version 1.0.1 from SourceForge. Use ONLY this version. Starting with release 1.1, the DITA toolkit is available under the Apache Software License. The recent version of the Tookit (as of this writing DITA-OT 1.1.2 under Apache License at http://sourceforge.net/projects/dita-ot/ ) should be verified to work with the Derby docs, then the instructions at http://db.apache.org/derby/manuals/dita.html updated accordingly. -- 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-486) Fix Error message X0X07 in doc to match string changes in code
[ http://issues.apache.org/jira/browse/DERBY-486?page=all ] Jeff Levitt updated DERBY-486: -- Fix Version: (was: 10.1.2.0) Fix Error message X0X07 in doc to match string changes in code -- Key: DERBY-486 URL: http://issues.apache.org/jira/browse/DERBY-486 Project: Derby Type: Sub-task Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 This is a subtask of DERBY-483 to match the string changes in the documentation. -- 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-566) Doc bug for saving ij output to a file
[ http://issues.apache.org/jira/browse/DERBY-566?page=all ] Jeff Levitt updated DERBY-566: -- Attachment: derby566.diff ttoolsij98878.html Attached patch fixes as requested, and html file is included for review. Wanted to get this in before the cutoff... Doc bug for saving ij output to a file -- Key: DERBY-566 URL: http://issues.apache.org/jira/browse/DERBY-566 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0 Reporter: Jeff Levitt Priority: Minor Fix For: 10.2.0.0, 10.1.2.0 Attachments: derby566.diff, ttoolsij98878.html Tracking issue as discussed in: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200509.mbox/[EMAIL PROTECTED] On the following page: http://db.apache.org/derby/docs/dev/tools/ttoolsij98878.html this is what needs to change on that page: - 2nd bullet on page, 'Redirect standard input to come from a file', the example should be: java -Djdbc.drivers=org.apache.derby.jdbc.EmbeddedDriver org.apache.derby.tools.ij *myscript.sql* - 5th bullet on page, 'By redirecting to a file', the example should be: java -Djdbc.drivers=org.apache.derby.jdbc.EmbeddedDriver org.apache.derby.tools.ij *myscript.sql* *myoutput.txt* -- 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-566) Doc bug for saving ij output to a file
Doc bug for saving ij output to a file -- Key: DERBY-566 URL: http://issues.apache.org/jira/browse/DERBY-566 Project: Derby Type: Bug Components: Documentation Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.2.0, 10.1.1.0 Tracking issue as discussed in: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200509.mbox/[EMAIL PROTECTED] On the following page: http://db.apache.org/derby/docs/dev/tools/ttoolsij98878.html this is what needs to change on that page: - 2nd bullet on page, 'Redirect standard input to come from a file', the example should be: java -Djdbc.drivers=org.apache.derby.jdbc.EmbeddedDriver org.apache.derby.tools.ij *myscript.sql* - 5th bullet on page, 'By redirecting to a file', the example should be: java -Djdbc.drivers=org.apache.derby.jdbc.EmbeddedDriver org.apache.derby.tools.ij *myscript.sql* *myoutput.txt* -- 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-544) Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS
[ http://issues.apache.org/jira/browse/DERBY-544?page=comments#action_12320450 ] Jeff Levitt commented on DERBY-544: --- This looks good to me, can we commit? Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS --- Key: DERBY-544 URL: http://issues.apache.org/jira/browse/DERBY-544 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0 Reporter: Oyvind Bakksjo Assignee: Oyvind Bakksjo Priority: Trivial Fix For: 10.2.0.0 Attachments: DERBY-544.diff, DERBY-544.status The admin guide at http://db.apache.org/derby/docs/10.1/adminguide/cadminappsclienttracing.html lists the various tracing constants for the Network Client. It lists the value of the TRACE_RESULT_SET_CALLS constant as 0x3; the correct value is 0x4. -- 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-484) Documentation for derby.database.classpath in developers guide is misleading
[ http://issues.apache.org/jira/browse/DERBY-484?page=all ] Jeff Levitt updated DERBY-484: -- Attachment: derby484.diff cdevdeploy21645.html Attached patch removes the content as requested. HTML output file is included for review. Documentation for derby.database.classpath in developers guide is misleading Key: DERBY-484 URL: http://issues.apache.org/jira/browse/DERBY-484 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.1 Reporter: Daniel John Debrunner Priority: Minor Attachments: cdevdeploy21645.html, derby484.diff 10.1 alpha docs (from site) http://db.apache.org/derby/docs/devguide/cdevdeploy21645.html 1) Remove sentence 'The first time you set the property, you must reboot to load the classes.' This is not true and is tested with lang/dcl.sql 2) This implies there is more infomation in the tuning guide, but I don't see any. 'See derby.database.classpath in Tuning Derby for more information about the property.' Searching the tuning guide I find no mention of derby.database.classpath http://db.apache.org/derby/docs/tuning/tuningderby.pdf -- 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-487) Getting Started Guide has reference to incubator URL
[ http://issues.apache.org/jira/browse/DERBY-487?page=all ] Jeff Levitt updated DERBY-487: -- Attachment: derbyinc.diff Here's a patch that changes the word incubator in the URL to db. Getting Started Guide has reference to incubator URL Key: DERBY-487 URL: http://issues.apache.org/jira/browse/DERBY-487 Project: Derby Type: Task Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Trivial Fix For: 10.1.1.0, 10.2.0.0 Attachments: derbyinc.diff On http://db.apache.org/derby/docs/getstart/cgsinstallingderby.html we have a reference to an incubator URL. Even though it will redirect, it should probably be changed to the new URL format. -- 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-489) Improvements to the related links for the Getting Started Guide
Improvements to the related links for the Getting Started Guide --- Key: DERBY-489 URL: http://issues.apache.org/jira/browse/DERBY-489 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Assigned to: Jeff Levitt Priority: Minor Fix For: 10.1.1.1, 10.2.0.0 Attachments: derbygsreltableupdates.diff Creating an entry to submit the patch discussed here: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200507.mbox/[EMAIL PROTECTED] With no negative feedback and approval from some as discussed here: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200508.mbox/[EMAIL PROTECTED] View the output here: http://derby.mylevita.com/getstart/ -- 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-489) Improvements to the related links for the Getting Started Guide
[ http://issues.apache.org/jira/browse/DERBY-489?page=all ] Jeff Levitt updated DERBY-489: -- Attachment: derbygsreltableupdates.diff Can we commit? Improvements to the related links for the Getting Started Guide --- Key: DERBY-489 URL: http://issues.apache.org/jira/browse/DERBY-489 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Assignee: Jeff Levitt Priority: Minor Fix For: 10.1.1.1, 10.2.0.0 Attachments: derbygsreltableupdates.diff Creating an entry to submit the patch discussed here: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200507.mbox/[EMAIL PROTECTED] With no negative feedback and approval from some as discussed here: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200508.mbox/[EMAIL PROTECTED] View the output here: http://derby.mylevita.com/getstart/ -- 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-486) Fix Error message X0X07 in doc to match string changes in code
Fix Error message X0X07 in doc to match string changes in code -- Key: DERBY-486 URL: http://issues.apache.org/jira/browse/DERBY-486 Project: Derby Type: Sub-task Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.1, 10.2.0.0 This is a subtask of DERBY-483 to match the string changes in the documentation. -- 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-487) Getting Started Guide has reference to incubator URL
Getting Started Guide has reference to incubator URL Key: DERBY-487 URL: http://issues.apache.org/jira/browse/DERBY-487 Project: Derby Type: Task Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Trivial Fix For: 10.1.1.0, 10.2.0.0 On http://db.apache.org/derby/docs/getstart/cgsinstallingderby.html we have a reference to an incubator URL. Even though it will redirect, it should probably be changed to the new URL format. -- 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-426) documentation need to be modified to reflect the derby-390 fix(once it is committed) , schem , table , column names need to be in case-sensitive form.
[ http://issues.apache.org/jira/browse/DERBY-426?page=all ] Jeff Levitt updated DERBY-426: -- Attachment: derby426modified.zip Attached patch includes Suresh's feedback. Please take a look at the included sample output and let me know if there are any other changes that need to be made. Thanks! documentation need to be modified to reflect the derby-390 fix(once it is committed) , schem , table , column names need to be in case-sensitive form. --- Key: DERBY-426 URL: http://issues.apache.org/jira/browse/DERBY-426 Project: Derby Type: Sub-task Components: Documentation Versions: 10.1.1.0 Reporter: Suresh Thalamati Attachments: derby426modified.zip Tools utilities Guide: Using bulk import/export chapter: BulkImport/ Arguments to the import procedure section: add the following in the end: If you created a schema, table or column name as a non-delimited identifier, you must pass the name in all upper case. If you created a schema, table or column name as a delimited identifier, you must pass the name in the same case as it was created. BulkExport/Arguments to the export procedure: add the following in the end: If you have created a schema or table name as a non-delimited identifier, you must pass the name in all upper case. If you created a schema or table name as a delimited identifier, you must pass the name in the same case as it was created. Examples of bulk import and export section: Add the following two examples to this section: The following example shows how to import data into the Order table (this table was created using delimited quotes to specify the name becuase the word 'Order' is a SQL reserved word) table in a sample database from the myfile.del file. CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE (null,'Order','myfile.del',null,null,null,0); The following example shows how to export data from the Order table (this table was created using delimited quotes to specify the name becuase the word 'Order' is a SQL reserved word) in a sample database from the myfile.del file. CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE (null,'Order','myfile.del',null,null,null); Modify the table name 'staff' to all upper case 'STAFF' for all import/export statements except for EXPORT_QUERY example. for example: CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE (null,'staff','myfile.del',null,null, null,0); toCALL SYSCS_UTIL.SYSCS_IMPORT_TABLE (null,'STAFF,'myfile.del',null,null,null,0); Importing into tables with identity columns section : modify table name 'tab1' to 'TAB1' and all column names also to upper case: CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'tab1', 'c1,c3,c4' , null, 'myfile.del',null, null,null,0) to CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'TAB1', 'C1,C3,C4' , null, 'myfile.del',null, null,null,0) CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'tab1', 'c1,c3,c4' , '1,3,4','empfile.del',null, null,null,0) to CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'TAB1', 'C1,C3,C4' , '1,3,4','empfile.del',null, null,null,0) Executing import/export procedures from JDBC: modify ps.setString(2,staff); to ps.setString(2,STAFF); CODESET values for import/export section: CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE (NULL,'staff','staff.dat',NULL,NULL,'UTF-8') to CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE(NULL,'STAFF','staff.dat',NULL,NULL,'UTF-8') and CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE(NULL,'STAFF','staff.dat',NULL,NULL,'UTF-8',0) In the REFERENCE Book Please do the following changes to import/export procedures: SYSCS_UTIL.SYSCS_EXPORT_TABLE: add the following before the example: If you have created a schema or table name as a non-delimited identifier, you must pass the name in all upper case. If you created a schema or table name as a delimited identifier, you must pass the name in the same case as it was created. modify tablename 'staff' to upper case 'STAFF' CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE (null, 'staff', 'myfile.del', null, null, null) to CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE (null, 'STAFF', 'myfile.del', null, null, null) SYSCS_UTIL.SYSCS_IMPORT_TABLE section: add the following before the example: If you created a schema or table name as a non-delimited identifier, you must pass the name in all upper case. If you created a schema or table name as a delimited identifier, you must pass the name in the same case as it was created. modify table name 'staff' to 'STAFF' CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE(null, 'staff', 'c:/output/myfile.del', ';', '%', null,0); to CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE(null, 'STAFF', 'c:/output/myfile.del', ';', '%', null,0); SYSCS_UTIL.SYSCS_IMPORT_DATA section: If you created a schema, table or column name as a non-delimited identifier, you must
[jira] Updated: (DERBY-426) documentation need to be modified to reflect the derby-390 fix(once it is committed) , schem , table , column names need to be in case-sensitive form.
[ http://issues.apache.org/jira/browse/DERBY-426?page=all ] Jeff Levitt updated DERBY-426: -- Attachment: derby426.zip Attached zip includes the patch as requested plus sample html output for all of the files affected. If this is OK, can we commit this to the main codeline as well as the 10.1 branch? How do we do that? documentation need to be modified to reflect the derby-390 fix(once it is committed) , schem , table , column names need to be in case-sensitive form. --- Key: DERBY-426 URL: http://issues.apache.org/jira/browse/DERBY-426 Project: Derby Type: Sub-task Components: Documentation Versions: 10.1.1.0 Reporter: Suresh Thalamati Attachments: derby426.zip Tools utilities Guide: Using bulk import/export chapter: BulkImport/ Arguments to the import procedure section: add the following in the end: If you created a schema, table or column name as a non-delimited identifier, you must pass the name in all upper case. If you created a schema, table or column name as a delimited identifier, you must pass the name in the same case as it was created. BulkExport/Arguments to the export procedure: add the following in the end: If you have created a schema or table name as a non-delimited identifier, you must pass the name in all upper case. If you created a schema or table name as a delimited identifier, you must pass the name in the same case as it was created. Examples of bulk import and export section: Add the following two examples to this section: The following example shows how to import data into the Order table (this table was created using delimited quotes to specify the name becuase the word 'Order' is a SQL reserved word) table in a sample database from the myfile.del file. CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE (null,'Order','myfile.del',null,null,null,0); The following example shows how to export data from the Order table (this table was created using delimited quotes to specify the name becuase the word 'Order' is a SQL reserved word) in a sample database from the myfile.del file. CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE (null,'Order','myfile.del',null,null,null); Modify the table name 'staff' to all upper case 'STAFF' for all import/export statements except for EXPORT_QUERY example. for example: CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE (null,'staff','myfile.del',null,null, null,0); toCALL SYSCS_UTIL.SYSCS_IMPORT_TABLE (null,'STAFF,'myfile.del',null,null,null,0); Importing into tables with identity columns section : modify table name 'tab1' to 'TAB1' and all column names also to upper case: CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'tab1', 'c1,c3,c4' , null, 'myfile.del',null, null,null,0) to CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'TAB1', 'C1,C3,C4' , null, 'myfile.del',null, null,null,0) CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'tab1', 'c1,c3,c4' , '1,3,4','empfile.del',null, null,null,0) to CALL SYSCS_UTIL.SYSCS_IMPORT_DATA (NULL, 'TAB1', 'C1,C3,C4' , '1,3,4','empfile.del',null, null,null,0) Executing import/export procedures from JDBC: modify ps.setString(2,staff); to ps.setString(2,STAFF); CODESET values for import/export section: CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE (NULL,'staff','staff.dat',NULL,NULL,'UTF-8') to CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE(NULL,'STAFF','staff.dat',NULL,NULL,'UTF-8') and CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE(NULL,'STAFF','staff.dat',NULL,NULL,'UTF-8',0) In the REFERENCE Book Please do the following changes to import/export procedures: SYSCS_UTIL.SYSCS_EXPORT_TABLE: add the following before the example: If you have created a schema or table name as a non-delimited identifier, you must pass the name in all upper case. If you created a schema or table name as a delimited identifier, you must pass the name in the same case as it was created. modify tablename 'staff' to upper case 'STAFF' CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE (null, 'staff', 'myfile.del', null, null, null) to CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE (null, 'STAFF', 'myfile.del', null, null, null) SYSCS_UTIL.SYSCS_IMPORT_TABLE section: add the following before the example: If you created a schema or table name as a non-delimited identifier, you must pass the name in all upper case. If you created a schema or table name as a delimited identifier, you must pass the name in the same case as it was created. modify table name 'staff' to 'STAFF' CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE(null, 'staff', 'c:/output/myfile.del', ';', '%', null,0); to CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE(null, 'STAFF', 'c:/output/myfile.del', ';', '%', null,0); SYSCS_UTIL.SYSCS_IMPORT_DATA section: If you created a schema, table or column name as a non-delimited
[jira] Created: (DERBY-460) Create error message documentation out of code
Create error message documentation out of code -- Key: DERBY-460 URL: http://issues.apache.org/jira/browse/DERBY-460 Project: Derby Type: Improvement Components: Build tools Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 As David suggested in the following thread: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200507.mbox/[EMAIL PROTECTED] We need a way to generate a DITA file for the Reference Manual from the messages themselves, so that when new messages are added or changes are made, they are propogated to the documentation. The requirements are: - Some way of keeping metadata for the DITA file (parameter values, user response, explanation) in comments within the messages file, or perhaps using an XML document to store the data and the strings? - A script or xsl transform that reads the messages and generates the DITA file, adding the metadata where necessary. - A script to do a one-time conversion of the DITA file to the messages file (whether it be the current method of storing message plus comments or an XML file) so that existing messages will be in the new format. Then, any new messages must follow the format. -- 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-377) There is no information available in the manuals on how to upgrade a database from 10.0 to 10.1 version.
[ http://issues.apache.org/jira/browse/DERBY-377?page=all ] Jeff Levitt updated DERBY-377: -- Attachment: derby377addendum.diff Thanks for the catch Andrew. I guess I didnt svn add it the first time. The attached patch called derby377addendum.diff is an update. It only includes that missing file. I assumed thats what you wanted since the others have already been committed. Let me know if you wanted a full patch. As for the sample output, its already in the first patch zip file. There is no information available in the manuals on how to upgrade a database from 10.0 to 10.1 version. Key: DERBY-377 URL: http://issues.apache.org/jira/browse/DERBY-377 Project: Derby Type: Bug Components: Documentation Versions: 10.1.1.0 Reporter: Suresh Thalamati Fix For: 10.1.1.0 Attachments: derby377addendum.diff, derby377modified.zip I could not find any info in the 10.1 Alpha manuals on how to upgrade a 10.0 database to use a 10.1 engine in full upgrade mode or software mode. I think this feature is implemented in the 10.1 code line , but not documented yet. -- 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-380) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Developer's Guide
[ http://issues.apache.org/jira/browse/DERBY-380?page=all ] Jeff Levitt updated DERBY-380: -- Attachment: derby380.diff The attached patch makes the changes requested in this doc review. I have created sample output on my own site: HTML files: http://derby.mylevita.com/devguide/ PDF: http://derby.mylevita.com/devguide/derbydev.pdf The patch affects EVERY dita file, but not the content for each file. This is because I modified the year in the dita source file copyrights for each file from 2004 to 2005. So while every file is listed in the patch, the only changes that will appear in the PDF and HTML files are those requested in this doc review. Also, note that I have made the change to the trademarks page in the same way that I did to the Getting Started guide patch in http://issues.apache.org/jira/browse/DERBY-379. Doc Review (CLOSED TO FURTHER COMMENTS): Derby Developer's Guide Key: DERBY-380 URL: http://issues.apache.org/jira/browse/DERBY-380 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 Attachments: derby380.diff This issue tracks comments for the Derby Developer's Guide. The deadline for posting comments was Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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-408) Fix formatting of manuals in PDF output
[ http://issues.apache.org/jira/browse/DERBY-408?page=all ] Jeff Levitt updated DERBY-408: -- Summary: Fix formatting of manuals in PDF output (was: Fix formatting of syntax sections in manuals) Description: 1. The syntax boxes in many of the Derby manuals seem to output with extra End-of-line feeds in the PDF's. Some syntax boxes print one word per line. For example: http://incubator.apache.org/derby/docs/tools/tools-single.html#rtoolsijpropref10135 This might be a bug with the DITA toolkit, because the DITA source files dont have these End-of-line feeds in them. This bug was originally reported in the doc reviews for version 10.1: http://issues.apache.org/jira/browse/DERBY-383 (see Myrna's comments) 2. Based on http://issues.apache.org/jira/browse/DERBY-384 comments to the doc review (see Sunitha's comments), we need to figure out how to et the table numbers to ascend. Currently, they all output as table 1. was: The syntax boxes in many of the Derby manuals seem to output with extra End-of-line feeds in the PDF's. Some syntax boxes print one word per line. For example: http://incubator.apache.org/derby/docs/tools/tools-single.html#rtoolsijpropref10135 This might be a bug with the DITA toolkit, because the DITA source files dont have these End-of-line feeds in them. This bug was originally reported in the doc reviews for version 10.1: http://issues.apache.org/jira/browse/DERBY-383 (see Myrna's comments) I am changing this bug to be more inclusive of other fixes needed for the PDF output. Fix formatting of manuals in PDF output --- Key: DERBY-408 URL: http://issues.apache.org/jira/browse/DERBY-408 Project: Derby Type: Bug Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 1. The syntax boxes in many of the Derby manuals seem to output with extra End-of-line feeds in the PDF's. Some syntax boxes print one word per line. For example: http://incubator.apache.org/derby/docs/tools/tools-single.html#rtoolsijpropref10135 This might be a bug with the DITA toolkit, because the DITA source files dont have these End-of-line feeds in them. This bug was originally reported in the doc reviews for version 10.1: http://issues.apache.org/jira/browse/DERBY-383 (see Myrna's comments) 2. Based on http://issues.apache.org/jira/browse/DERBY-384 comments to the doc review (see Sunitha's comments), we need to figure out how to et the table numbers to ascend. Currently, they all output as table 1. -- 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-382) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual
[ http://issues.apache.org/jira/browse/DERBY-382?page=all ] Jeff Levitt updated DERBY-382: -- Comment: was deleted Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual --- Key: DERBY-382 URL: http://issues.apache.org/jira/browse/DERBY-382 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 This issue tracks comments for the Derby Reference Manual. The deadline for posting comments was Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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-384) Doc Review (CLOSED TO FURTHER COMMENTS): Tuning Derby
[ http://issues.apache.org/jira/browse/DERBY-384?page=all ] Jeff Levitt updated DERBY-384: -- Attachment: derby384.diff The attached patch makes the changes requested in this doc review. I have created sample output on my own site: HTML files: http://derby.mylevita.com/tuning/ PDF: http://derby.mylevita.com/tuning/tuningderby.pdf The patch affects EVERY dita file, but not the content for each file. This is because I modified the year in the dita source file copyrights for each file from 2004 to 2005. So while every file is listed in the patch, the only changes that will appear in the PDF and HTML files are those requested in this doc review. For references to ToursDB, I have replaced them with sample, but I doubt the examples would work against the samples database. Since I didn't have examples to replace all of the toursDB examples, my main concern was making sure the code would work; not necessarily whether they would work in a specific db. It would be nice later on to get some examples for many of these sections that would work in the sample db. Also, note that I have made the change to the trademarks page in the same way that I did to the Getting Started guide patch in http://issues.apache.org/jira/browse/DERBY-379. Doc Review (CLOSED TO FURTHER COMMENTS): Tuning Derby - Key: DERBY-384 URL: http://issues.apache.org/jira/browse/DERBY-384 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 Attachments: derby384.diff This issue tracks comments for the manual known as Tuning Derby. The deadline for posting comments was Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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-382) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual
[ http://issues.apache.org/jira/browse/DERBY-382?page=all ] Jeff Levitt updated DERBY-382: -- Attachment: derby382.diff The attached patch makes the changes requested in this doc review. I have created sample output on my own site: HTML files: http://derby.mylevita.com/tools/ PDF: http://derby.mylevita.com/tools/derbytools.pdf The patch affects EVERY dita file, but not the content for each file. This is because I modified the year in the dita source file copyrights for each file from 2004 to 2005. So while every file is listed in the patch, the only changes that will appear in the PDF and HTML files are those requested in this doc review. I was not able to incorporate several requests due to the need for either more input or more time. I have created a new JIRA issue for fix in 10.2 outlining these requirements. It is http://issues.apache.org/jira/browse/DERBY-423 Also, note that I have made the change to the trademarks page in the same way that I did to the Getting Started guide patch in http://issues.apache.org/jira/browse/DERBY-379. Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual --- Key: DERBY-382 URL: http://issues.apache.org/jira/browse/DERBY-382 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 Attachments: derby382.diff This issue tracks comments for the Derby Reference Manual. The deadline for posting comments was Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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-382) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual
[ http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314834 ] Jeff Levitt commented on DERBY-382: --- Forgot to change the links in my posting template to point to the ref manual on my site: http://derby.mylevita.com/ref/refderby.pdf http://derby.mylevita.com/ref/ Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual --- Key: DERBY-382 URL: http://issues.apache.org/jira/browse/DERBY-382 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 Attachments: derby382.diff This issue tracks comments for the Derby Reference Manual. The deadline for posting comments was Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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-380) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Developer's Guide
[ http://issues.apache.org/jira/browse/DERBY-380?page=comments#action_12314839 ] Jeff Levitt commented on DERBY-380: --- Suresh requested in Derby-377 (too late for that commit): In preparing for Upgrade section , Following step is not required: 1. Force a checkpoint with the earlier version of Derby. To force a checkpoint, connect to the database with the older version of the Derby software and issue a shutdown request using the shutdown=true attribute on the database connection URL, as shown in the following example: /* in a java program */ DriverManager.getConnection(jdbc:derby:sample;shutdown=true); Doc Review (CLOSED TO FURTHER COMMENTS): Derby Developer's Guide Key: DERBY-380 URL: http://issues.apache.org/jira/browse/DERBY-380 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 This issue tracks comments for the Derby Developer's Guide. The deadline for posting comments was Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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-379) Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby
[ http://issues.apache.org/jira/browse/DERBY-379?page=all ] Jeff Levitt updated DERBY-379: -- Attachment: derby379.diff The attached patch makes the changes requested in this doc review. I have created sample output on my own site: HTML files: http://derby.mylevita.com/getstart/ PDF: http://derby.mylevita.com/getstart/getstartderby.pdf A couple of items to note: The patch affects EVERY dita file, but not the content for each file. This is because I modified the year in the dita source file copyrights for each file from 2004 to 2005. So while every file is listed in the patch, the only changes that will appear in the PDF and HTML files are those requested in this doc review. I also made some changes to the trademarks page (The last section in the manual). This page listed trademarks for other companies. While the Microsoft, Sun, and Open Group trademarks appeared normal, the IBM tradmarks were in a table that was not appearing. It didn't make sense to be placing the IBM trademarks in a table while the other companies were not, so I deleted the table and rewrote the IBM trademarks in a sentence just like the others. Please see: http://derby.mylevita.com/getstart/rgstrademderby.html (you can compare it to our existing page: http://incubator.apache.org/derby/docs/getstart/rgstrademderby.html While the table currently shows up fine in that HTML link, it does not appear in the current PDF's) This page appears the same in all 6 books, so I would also apply this change to the docs in each of their respective doc review patches. I think this section needs to be carefully reviewed with the rest of the changes made in this patch, as this is legal information concerning multiple companies and should not be taken lightly. Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby Key: DERBY-379 URL: http://issues.apache.org/jira/browse/DERBY-379 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 Attachments: derby379.diff This issue tracks comments for the Getting Started with Derby manual. The deadline for posting comments was Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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-379) Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby
[ http://issues.apache.org/jira/browse/DERBY-379?page=all ] Jeff Levitt updated DERBY-379: -- Attachment: derby379.diff Re-attaching patch...had some problems with the initial attachment process because of my connection... Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby Key: DERBY-379 URL: http://issues.apache.org/jira/browse/DERBY-379 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 Attachments: derby379.diff This issue tracks comments for the Getting Started with Derby manual. The deadline for posting comments was Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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-381) Doc review (CLOSED TO FURTHER COMMENTS): Derby Server and Admin Guide
[ http://issues.apache.org/jira/browse/DERBY-381?page=all ] Jeff Levitt updated DERBY-381: -- Attachment: derby381.diff The attached patch makes the changes requested in this doc review. I have created sample output on my own site: HTML files: http://derby.mylevita.com/adminguide/ PDF: http://derby.mylevita.com/adminguide/derbyadmin.pdf The patch affects EVERY dita file, but not the content for each file. This is because I modified the year in the dita source file copyrights for each file from 2004 to 2005. So while every file is listed in the patch, the only changes that will appear in the PDF and HTML files are those requested in this doc review. Also, note that I have made the change to the trademarks page in the same way that I did to the Getting Started guide patch in Derby-379. Doc review (CLOSED TO FURTHER COMMENTS): Derby Server and Admin Guide - Key: DERBY-381 URL: http://issues.apache.org/jira/browse/DERBY-381 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 Attachments: derby381.diff This issue tracks comments for the Derby Server and Administration Guide. The deadline for posting comments WAS Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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-408) Fix formatting of syntax sections in manuals
Fix formatting of syntax sections in manuals Key: DERBY-408 URL: http://issues.apache.org/jira/browse/DERBY-408 Project: Derby Type: Bug Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.2.0.0 The syntax boxes in many of the Derby manuals seem to output with extra End-of-line feeds in the PDF's. Some syntax boxes print one word per line. For example: http://incubator.apache.org/derby/docs/tools/tools-single.html#rtoolsijpropref10135 This might be a bug with the DITA toolkit, because the DITA source files dont have these End-of-line feeds in them. This bug was originally reported in the doc reviews for version 10.1: http://issues.apache.org/jira/browse/DERBY-383 (see Myrna's comments) -- 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-383) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Tools and Utilities Guide
[ http://issues.apache.org/jira/browse/DERBY-383?page=all ] Jeff Levitt updated DERBY-383: -- Attachment: derby383.diff The attached patch makes the changes requested in this doc review. I have created sample output on my own site: HTML files: http://derby.mylevita.com/tools/ PDF: http://derby.mylevita.com/tools/derbytools.pdf The patch affects EVERY dita file, but not the content for each file. This is because I modified the year in the dita source file copyrights for each file from 2004 to 2005. So while every file is listed in the patch, the only changes that will appear in the PDF and HTML files are those requested in this doc review. Also, note that I have made the change to the trademarks page in the same way that I did to the Getting Started guide patch in http://issues.apache.org/jira/browse/DERBY-379. Doc Review (CLOSED TO FURTHER COMMENTS): Derby Tools and Utilities Guide Key: DERBY-383 URL: http://issues.apache.org/jira/browse/DERBY-383 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 Attachments: derby383.diff This issue tracks comments for the Derby Tools and Utilities Guide. The deadline for posting comments was Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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-382) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual
[
http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314720 ]
Jeff Levitt commented on DERBY-382:
---
Adding Kathey Marsden's comment on Derby-275 that was added after that issue
was committed:
REGARDING THIS PARAGRAPH:
Note that unlike a GENERATED ALWAYS column, a GENERATED BY DEFAULT column does
not guarantee uniqueness. Thus, in the above example, the hi and salut rows
will both have an identity value of 1, because the generated column starts at
1 and the user-specified value was also 1. To prevent this, you can use the
STARTS WITH keyword described below. To check for this condition and disallow
it, you can use a primary key or unique constraint on the GENERATED BY DEFAULT
identity column.
In the paragraph STARTS WITH should be START WITH and loading or importing data
should be covered.
CHANGE:
To prevent this, you can use the STARTS WITH keyword described below.
TO:
To prevent duplication especially when loading or importing data, create the
table using a START WITH value which corresponds to the first
identity value that the system should assign.
ADD AN EXAMPLE:
create table greetings
(i int generated by default as identity (START WITH 2, INCREMENT BY 1),
ch char(50));
-- specify value 1:
insert into greetings values (1, 'hi');
-- use generated default
insert into greetings values (DEFAULT, 'salut');
-- use generated default
insert into greetings(ch) values ('bonjour');
Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual
---
Key: DERBY-382
URL: http://issues.apache.org/jira/browse/DERBY-382
Project: Derby
Type: Improvement
Components: Documentation
Environment: all
Reporter: Jeff Levitt
Priority: Minor
Fix For: 10.1.1.0
This issue tracks comments for the Derby Reference Manual. The deadline for
posting comments was Tuesday, June 28, noon Pacific time.
PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have
additional comments, please open a JIRA issue for a fixin in a future
release, as there is not enough time to incorporate additional comments.
Some guidelines to follow when posting comments to this issue are:
- Try to make clear and concise comments about what you want changed whenever
possible. Provide concrete comments that say Please change original to
modified instead of generic comments like This section needs to be
rewritten.
- If you're reviewing the HTML Files copy, include the URL for the page in
the review comment. Obtain the URL like this:
* highlight the topic in the left frame
* right click
* choose Properties
* copy and paste the address in the pop up box.
- If you're reviewing the PDF copy, in the review comment:
* Include the page number for the PDF, and indicate whether the number is
the PDF sheet number or the printed page number.
* Include the title of the section that the problem occurs in. If it's in
a subsection, try to include the hierarchy of titles.
- Please don't review the HTML Book copy -- it'll be time consuming to match
up that copy with the underlying DITA source.
--
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] Resolved: (DERBY-166) NULL is not a valid constraint type
[ http://issues.apache.org/jira/browse/DERBY-166?page=all ] Jeff Levitt resolved DERBY-166: --- Resolution: Duplicate I am adding this comment to the doc review for the reference manual for version 10.1. It will get patched there... Thus, resolving this issue as a duplicate of Derby-382... NULL is not a valid constraint type --- Key: DERBY-166 URL: http://issues.apache.org/jira/browse/DERBY-166 Project: Derby Type: Bug Components: Documentation Versions: 10.0.2.0 Environment: Windows XP SP1 Professional Reporter: George Baklarz Priority: Trivial The following statement in the documentation is incorrect: NULL The opposite of NOT NULL (not really a constraint), it specifies that the column can hold NULL values. Specifying NULL is the same as saying nothing at all, except when the column is included in a PRIMARY KEY constraint. If you try to create a column with the NULL attribute, you get a failure: CREATE TABLE X ( A INT NULL ); ERROR 42X01: Syntax error: Encountered null at line 1, column 23. While this isn't really a problem since we can just omit the NULL keyword, the documentation gives the impression that it is allowed in the CREATE statement. -- 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-382) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual
[ http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314722 ] Jeff Levitt commented on DERBY-382: --- From Derby-166 (which is resolved as a duplicate of this issue now): The following statement in the documentation is incorrect: NULL The opposite of NOT NULL (not really a constraint), it specifies that the column can hold NULL values. Specifying NULL is the same as saying nothing at all, except when the column is included in a PRIMARY KEY constraint. If you try to create a column with the NULL attribute, you get a failure: CREATE TABLE X ( A INT NULL ); ERROR 42X01: Syntax error: Encountered null at line 1, column 23. While this isn't really a problem since we can just omit the NULL keyword, the documentation gives the impression that it is allowed in the CREATE statement. Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual --- Key: DERBY-382 URL: http://issues.apache.org/jira/browse/DERBY-382 Project: Derby Type: Improvement Components: Documentation Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.1.1.0 This issue tracks comments for the Derby Reference Manual. The deadline for posting comments was Tuesday, June 28, noon Pacific time. PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have additional comments, please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate additional comments. Some guidelines to follow when posting comments to this issue are: - Try to make clear and concise comments about what you want changed whenever possible. Provide concrete comments that say Please change original to modified instead of generic comments like This section needs to be rewritten. - If you're reviewing the HTML Files copy, include the URL for the page in the review comment. Obtain the URL like this: * highlight the topic in the left frame * right click * choose Properties * copy and paste the address in the pop up box. - If you're reviewing the PDF copy, in the review comment: * Include the page number for the PDF, and indicate whether the number is the PDF sheet number or the printed page number. * Include the title of the section that the problem occurs in. If it's in a subsection, try to include the hierarchy of titles. - Please don't review the HTML Book copy -- it'll be time consuming to match up that copy with the underlying DITA source. -- 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
