db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-5056) Incorrect statement in reference manual about memory requirement when streaming columns
Date Tue, 01 Mar 2011 11:24:36 GMT

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

Knut Anders Hatlen commented on DERBY-5056:

Thanks, Kim. I think you're right that we only need to remove that item. I cannot think of
anything we need to add. +1 to commit.

> Incorrect statement in reference manual about memory requirement when streaming columns
> ---------------------------------------------------------------------------------------
>                 Key: DERBY-5056
>                 URL: https://issues.apache.org/jira/browse/DERBY-5056
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-5056.diff, rrefjavsqlprst.html
> The reference manual says the following about memory requirements when streaming columns
from the network client - http://db.apache.org/derby/docs/10.7/ref/rrefjavsqlprst.html:
> > For applications using the client driver, if the stream is stored in a column of
a type other than LONG VARCHAR or LONG VARCHAR FOR BIT DATA, the entire stream must be able
to fit into memory at one time. Streams stored in LONG VARCHAR and LONG VARCHAR FOR BIT DATA
columns do not have this limitation.
> I believe this is not true any more. There was a lot of work to reduce the memory requirements
for LOBs in Derby 10.2 and Derby 10.3, and I think the specific problem referred to in this
section of the manual was fixed in DERBY-550/DERBY-1301.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message