Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1566851898.1141424380301.JavaMail.jira@ajax.apache.org>
Date: Fri, 3 Mar 2006 23:19:40 +0100 (CET)
From: "Jeff Levitt (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-671) Clob.getCharacterStream documented as
 not supported when it actually is
In-Reply-To: <180924139.1130930515670.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ 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