db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Bradbury (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-380) Doc Review: Derby Developer's Guide
Date Fri, 24 Jun 2005 23:21:59 GMT
    [ http://issues.apache.org/jira/browse/DERBY-380?page=comments#action_12314438 ] 

Stan Bradbury commented on DERBY-380:

Stan's review of:  %%% Developers Guide:  Derby and Standards %%%

 >> ON PAGE: http://incubator.apache.org/derby/docs/devguide/cdevstandards805690.html
   **  REPLACE: Derby uses its own system catalog and JDBC's DatabaseMetadata, and does not
provide the standard Information Schema views.
   **  NEW: Derby uses its own system catalog that can be accessed via standard JDBC DatabaseMetadata
calls.  Derby does not provide the standard Information Schema views.

  >> ON PAGE: http://incubator.apache.org/derby/docs/devguide/cdevstandards805716.html
    ** REPLACE: Derby uses JDBC's Connection, and provides only the SQL command SET TRANSACTION
ISOLATION for transactions.
    **  NEW: All operations in Derby are transactional.  Derby supports transaction control
via JDBC 3.0 Connection methods.  This includes savepoints and support for the four JDBC transaction
isolation levels.  The only SQL command provided for transaction control is SET TRANSACTION

  >> ON PAGE:
	(Calling functions and procedures)
    ** ADD after the existing sentence:  Built in functions and user defined functions declared
with the CREATE FUNCTION command can be called as part of an SQL select statement or using
a VALUES clause or VALUES expression.

  >> REMOVE:
	( Fewer reserved keywords )
  ** REMOVE: This does not relate to the SQL99 standard and does not belong here.

  >> ON PAGE:
	(BLOB and CLOB)
   **  ADD:  BLOB and CLOB values are limited to a maximum of 2,147,483,647 characters.

> Doc Review: 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:

> This issue tracks comments for the Derby Developer's Guide. The deadline for posting
comments isTuesday, June 28, noon Pacific time.
> 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:
For more information on JIRA, see:

View raw message