db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1932) Reference Manual updates - JDBC Reference section
Date Tue, 19 Aug 2008 17:13:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623734#action_12623734

Kim Haase commented on DERBY-1932:

Some fixes are needed here to tidy up the JDBC reference section, though some have already
been made.

rrefjdbc96386.html -- this problem was fixed in DERBY-3409 (table entries with no implementation
notes are now gone).

rrefdmdfns.html (DatabaseMetaData functionality not supported): this topic was removed from
the manual at 10.3, it appears.

rrefjavsqlprst.html: Mention of JDBC 1.2 was removed in DERBY-3409. Not sure why note refers
to getXXXStream since only setXXXStream methods exist.

There was no indication in reviews of DERBY-3409 that setUnicodeStream was no longer implemented
in Derby. This is true, however (it throws a Feature not implemented exception).

Unless I hear otherwise, I will add info about setCharacterStream. I assume I can replace
setUnicodeStream with setCharacterStream in the table (that is, that LONGVARCHAR is the preferred
target data type). Please let me know if this is not the case.

Derby doesn't support setNCharacterStream/getNCharacterStream (throws Feature not implemented

Checking the 10.3 reference manual, it appears that it is the middle note that applies to
the client driver only. Is that the case? It would be hard to test this.

crefjavbclobnot.html (Notes on Blob/Clob): remove getUnicodeStream, add getCharacterStream.

It appears to be true that rrefjavsqlrssc.html (ResultSets) and rrefjdbc4_0summary.html need
no changes -- though rrefjavsqlrssc.html has an unused variable declaration ("int c:") that
could be removed.

> Reference Manual updates - JDBC Reference section
> -------------------------------------------------
>                 Key: DERBY-1932
>                 URL: https://issues.apache.org/jira/browse/DERBY-1932
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Laura Stewart
>            Assignee: Kim Haase
> JDBC Reference: 
> Section =  java.sql.Blob and java.sql.Clob 
> File = http://db.apache.org/derby/docs/10.2/ref/rrefjdbc96386.html 
> Update = 
> This section has a table titled Table 1. JDBC 2.0 java.sql.Blob Methods Supported. The
first row, 3rd column of this table shows up empty in the html page but has an ' in the pdf
format. The pdf format should also show the column empty. I think this happens for all the
tables with no data in the pdf format 
> Section = DatabaseMetaData functionality not supported 
> File =  http://db.apache.org/derby/docs/10.2/ref/ref-single.html#N2E3A9 
> Update =  
> This section says that getColumnPrivileges and getTablePrivileges are not supported.
But checkin r381109 has changes to metadata.properties for these 2 functions. So, looks like
these methods are probably now supported with grant revoke functionality. 
> Section = Data streaming 
> Files = 
> (1) http://db.apache.org/derby/docs/dev/ref/rrefjavsqlprst.html
> (2) http://db.apache.org/derby/docs/dev/ref/rrefjavsqlrssc.html
> (3) http://db.apache.org/derby/docs/dev/ref/crefjavbclobnot.html 
> (4) http://db.apache.org/derby/docs/dev/ref/rrefjdbc4_0summary.html
> Updates =  
> (1): Rewrite section to reflect a newer JDBC version than 1.2? Comment that getUnicodeStream
is deprecated and no longer implemented in Derby. Add description of getCharacterStream. Could
also add info about setNCharacterStream, which is JDBC 4 only and not supported. The note
under the table is no longer accurate; it only applies when using the client driver (and also
only for the client?).
> (2): OK 
> (3): Update list of methods (mark as deprecated, add getCharacterStream). 
> (4): OK.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message