db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-2827) Rename ClobStreamControl to TemporaryClob
Date Fri, 15 Jun 2007 13:04:26 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan closed DERBY-2827.
----------------------------------

    Resolution: Fixed

Committed to trunk with revision 547657.
Issue completed.

> 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
>
>         Attachments: derby-2827-1a.diff, derby-2827-1a.stat
>
>
> 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.


Mime
View raw message