Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Fri, 25 Aug 2006 14:57:04 +0200
From: Oystein Grovlen - Sun Norway <Oystein.Grovlen@Sun.COM>
Subject: Re: [jira] Commented: (DERBY-1292) ClassCastException in ClientDriver
 when using CLOB columns and batch updates
In-reply-to: <1053195.1156450699944.JavaMail.jira@brutus>
Sender: Oystein.Grovlen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <44EEF3A0.4060405@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 8BIT
References: <1053195.1156450699944.JavaMail.jira@brutus>
User-Agent: Thunderbird 1.5.0.5 (X11/20060730)

James F. Adams (JIRA) wrote:
 >     [ 
http://issues.apache.org/jira/browse/DERBY-1292?page=comments#action_12430315 
]
 >
 > James F. Adams commented on DERBY-1292:
 > ---------------------------------------
 >
 > Thanks for the review Øystein.  I have one question about item 6.  It 
appears that the jdbcapi/batchUpdate.java test is skipped when using the 
DerbyNetClient framework.  Should I add the test to both 
derbynet/perpStmt.java and jdbcapi/batchUpdate?

Oh, I did not notice this.  I tried to run batchUpdate with
DerbyNetClient, but this still fails.   I guess that means that beetle
5561 is still an issue (whatever that means; kind of proves my point
about using bug numbers in the code :-).

I will not require that you also add it to jdbcapi/batchUpdate in that
case, but it is probably a good idea.

-- 
Øystein