Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <1168548836.1128449337475.JavaMail.jira@ajax.apache.org>
Date: Tue, 4 Oct 2005 20:08:57 +0200 (CEST)
From: "Sunitha Kambhampati (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-352) Clobs on insert  using streams should not
 instantiate into memory
In-Reply-To: <1584617435.1118685410258.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-352?page=all ]

Sunitha Kambhampati updated DERBY-352:
--------------------------------------

    Attachment: Derby352.diff.txt

> Clobs on insert  using streams should not instantiate into memory
> -----------------------------------------------------------------
>
>          Key: DERBY-352
>          URL: http://issues.apache.org/jira/browse/DERBY-352
>      Project: Derby
>         Type: Bug
>   Components: JDBC, Performance, Store
>     Versions: 10.0.2.1, 10.0.2.0
>  Environment: all
>     Reporter: Sunitha Kambhampati
>     Assignee: Sunitha Kambhampati
>  Attachments: Derby352.diff.txt
>
> Currently in derby, for an insert on a clob using setCharacterStream what will happen is , the entire stream will be materialized into a char array and sent to store for the insert. 
> see  - SQLVarChar.normalize, where getString() is called and SQLChar.getString() will materiliaze the entire stream into a char array ( SQLChar.readExternal). 
> The store layer must actually drive the streaming. 

-- 
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