[
https://issues.apache.org/jira/browse/DERBY-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-3409:
-----------------------------
Attachment: DERBY-3409-2.stat
DERBY-3409-2.zip
DERBY-3409-2.diff
Here is a revised patch: DERBY-3409-2.diff, DERBY-3409-2.zip, and
DERBY-3409-2.stat.
Correspondence with Lance Andersen (JDBC expert) and Rick Hillegas, along with
an examination of the source code for Derby's JDBC implementation, has resulted
in the following additional changes.
rrefjdbc40794.dita (java.sql.Statement): Remove mention of JDBC 1.2. Also, the
setEscapeProcessing and cancel methods are still not implemented, but all the
others are supported.
rrefjdbc23502.dita (java.sql.ResultSet): Remove table row for setFetchSize; the
implementation seems to allow for fetch sizes greater than 1.
rrefjdbc96386.dita (Mapping of java.sql.Blob and java.sql.Clob interfaces):
Remove mention of JDBC 2.0. Explain that Derby implements the Blob and Clob
interfaces using locators and does not materialize LOBs when you use getBlob
and getClob on ResultSets. Remove bullet list of Blob and Clob features; state
only what is specific to the Derby implementation (the CallableStatement
limitations). Remove mention of other SQL data types (irrelevant to this
topic). Clarify the use of getBlob and getClob. Remove bullet item about static
methods. Update the information about CLOB implementation. Revise tables to
provide only implementation notes where needed.
Also added updated versions of rrefjdbc20485.dita (java.sql.CallableStatement
interface), rrefjdbc29874.dita (java.sql.PreparedStatement interface), and
rrefjavsqlprst.dita (Prepared statements and streaming columns), all of which
contained old (JDBC 1.2) information.
Please let me know if further corrections are needed.
> Remove JDBC 2.0-specific topics from Reference Manual and merge
> implementation notes as needed
> ----------------------------------------------------------------------------------------------
>
> Key: DERBY-3409
> URL: https://issues.apache.org/jira/browse/DERBY-3409
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Affects Versions: 10.3.2.1
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-3409-2.diff, DERBY-3409-2.stat, DERBY-3409-2.zip,
> DERBY-3409.diff, DERBY-3409.stat, DERBY-3409.zip
>
>
> The following files should be removed and their contents merged, where
> appropriate, with the main files for the interfaces concerned:
> JDBC 2.0 features (rrefjdbc2_0summary.dita): remove
> java.sql.CallableStatement interface: supported JDBC 2.0 methods
> (rrefjdbc52637.dita): remove
> java.sql.Connection interface: supported JDBC 2.0 methods
> (rrefjdbc80004.dita): remove? It appears that the implementation notes are no
> longer valid. They state that ResultSet.TYPE_SCROLL_SENSITIVE is not
> supported and that if you specify it, "Derby issues an SQLWarning". However,
> I tried this and no warning seemed to be issued.
> java.sql.DatabaseMetaData interface: supported JDBC 2.0 methods
> (rrefjdbc66688.dita): remove
> java.sql.PreparedStatement interface: supported JDBC 2.0 methods
> (rrefjdbc99392.dita): remove
> java.sql.ResultSet interface: supported JDBC 2.0 methods
> (rrefjdbc77156.dita): remove, after adding implementation notes to the topic
> "java.sql.ResultSet interface"
> (http://db.apache.org/derby/docs/dev/ref/rrefjdbc23502.html), assuming they
> are still valid. (Removing this file will allow us to resolve DERBY-2993,
> "Duplicated description of java.sql.ResultSet#beforeFirst() is written in
> reference manual".)
> java.sql.ResultSetMetaData interface: supported JDBC 2.0 methods
> (rrefjdbc71949.dita)
> java.sql.Statement interface: supported JDBC 2.0 methods
> (rrefjdbc59162.dita): if implementation notes are still valid, change title
> to "java.sql.Statement interface", move topic to the general JDBC reference
> section, remove table, and provide one-sentence implementation notes on the
> appropriate methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
