Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <8974464.1180968051149.JavaMail.jira@brutus>
Date: Mon, 4 Jun 2007 07:40:51 -0700 (PDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (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


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

Kristian Waagan updated DERBY-2646:
-----------------------------------

    Attachment: derby-2646-05a-tests.stat
                derby-2646-05a-tests.diff

'derby-2646-05a-tests.diff' contains a series of tests for Clob.
More tests can/should be added, they are far from complete.

There is one "normal" test, 'jdbcapi/ClobTest'. It is not enabled in any suite yet, as two of the tests fails with the current implementation due to UTFDataFormatException (which again is due to positioning/boundary errors). They will be enabled as part of the next patch for this issue.

There is also four package-private test classes, all based off the abstract superclass 'InternalClobTest'.
The test classes test the following cases:
  SmallStoreStreamTest: Small read-only Clobs from a store stream
  BiggerStoreStreamTest: Bigger read-only Clobs from a store stream, size should cause crossing of various buffer sizes and boundaries.
  SmallTemporaryClobTest: Temorary read-write Clobs held in memory.
  BiggerTemporaryClobTest:  Temporary read-write Clobs stored on disk due to their size.

Transition from read-only to read-write is not tested in the package-private tests, as transition is the responsibility of EmbedClob. I also considered adding encryption to BiggerTemporaryClobTest, but decided to put this on hold and address it in a later patch. I think we have some performance issues with encrypted Clobs, but it can be due to the test implementation and should be determined before any conclusions are taken.

The required framework for package-private tests are not in place. I will possibly address this later, but for now the package private tests must be compiled and run manually.
The simplest is to issue for instance this javac command from trunk after having compiled Derby the normal way:
javac -d classes/ -classpath classes/:tools/java/junit.jar java/testing/org/apache/derby/impl/jdbc/*java
Then run them with 'classes/' in the classpath:
java junit.textui.TestRunner org.apache.derby.impl.jdbc._Suite

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


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