Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <31299753.1181909907610.JavaMail.jira@brutus>
Date: Fri, 15 Jun 2007 05:18:27 -0700 (PDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-2827) Rename ClobStreamControl to
 TemporaryClob
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Rename ClobStreamControl to TemporaryClob
-----------------------------------------

                 Key: DERBY-2827
                 URL: https://issues.apache.org/jira/browse/DERBY-2827
             Project: Derby
          Issue Type: Improvement
          Components: JDBC
    Affects Versions: 10.3.0.0
            Reporter: Kristian Waagan
            Assignee: Kristian Waagan
            Priority: Trivial
             Fix For: 10.3.0.0


Since the original submission, the situation has changed quite a lot and the original name no longer fits as well as it did before.

The class is changed to TemporaryClob, signalling that the Clob object is living temporarily outside the database. This is true for all scenarios, except for small Clobs that are stored as non-stream objects in the database. 
The general contract is that as soon as a change is made to the Clob, it becomes a temporary Clob. Unless the user reinserts the Clob (i.e. updateRow, updateClob + execute), the changes will be lost. This is also true for Clobs created with Connection.createClob. If it is not explicitly inserted into the database, it is lost.

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