Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 92943 invoked from network); 5 Jun 2007 13:48:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Jun 2007 13:48:48 -0000 Received: (qmail 46267 invoked by uid 500); 5 Jun 2007 13:48:51 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 46052 invoked by uid 500); 5 Jun 2007 13:48:51 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 46038 invoked by uid 99); 5 Jun 2007 13:48:51 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2007 06:48:51 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2007 06:48:46 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 724B8714199 for ; Tue, 5 Jun 2007 06:48:26 -0700 (PDT) Message-ID: <32238198.1181051306465.JavaMail.jira@brutus> Date: Tue, 5 Jun 2007 06:48:26 -0700 (PDT) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2646) Cleanup of Clob control/support structures In-Reply-To: <23467132.1179212896142.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501559 ] Kristian Waagan commented on DERBY-2646: ---------------------------------------- I was planning to use it to ensure visibility of the variable without having to obtain a lock. This it achieves, but since release() is closing the store stream as well, I need to obtain a lock to ensure the stream is not closed while an operation is being performed on it. Thus the volatile modifier must go away (I will fix this at once). And the reason why you don't understand much of the synchronization policy, is because it is not yet in place :) The task grew a bit bigger than expected, and I need to push it out to "get things done". It is also bad to track all these things under this issue. I have created DERBY-2762 to track the synchronization issue. There are also some related issues already filed, and I hope we can link them up soon. Even though there are important things not yet addressed regarded to Clob, all our tests passes... As a little warning, we might see some instabilities related to Clobs. There are two reasons; this rewrite on the embedded side, and the enabling of locator support on the client side. I think we should get these improvements into trunk ASAP and then address the remaining issues. > Cleanup of Clob control/support structures > ------------------------------------------ > > Key: DERBY-2646 > URL: https://issues.apache.org/jira/browse/DERBY-2646 > Project: Derby > Issue Type: Sub-task > Components: JDBC > Affects Versions: 10.3.0.0 > Reporter: Kristian Waagan > Assignee: Kristian Waagan > Fix For: 10.3.0.0 > > Attachments: derby-2646-01a_trailing_space.diff, derby-2646-01a_trailing_space.stat, derby-2646-02a-clob-reorg.diff, derby-2646-02a-clob-reorg.stat, derby-2646-03a-internalclob.diff, derby-2646-04a-storestreamclob_utf8util.diff, derby-2646-04a-storestreamclob_utf8util.stat, derby-2646-04b-storestreamclob_utf8util.diff, derby-2646-05a-tests.diff, derby-2646-05a-tests.stat, derby-2646-05b-tests.diff > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.