db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sunitha Kambhampati <ksunitha...@gmail.com>
Subject Re: [PATCH] Derby 218 - Add relaxed durability option
Date Wed, 11 May 2005 18:19:14 GMT
Sunitha Kambhampati wrote:

> David Van Couvering wrote:
>
>> Great!  I have a question: if I wanted to use this to speed up 
>> testing, how do I do it within the context of the test harness?
>>
> To enable this mode for derbyall suite.
> put the following property in 
> java\testing\org\apache\derbyTesting\functionTests\suites\derbyall.properties 
>
> derby.system.durability=test
>
> build it ( ant testing).
>
> Then I believe, when you run derbyall, this property will be picked up 
> by all the tests run as part of derbyall.
>
Also, if you want to doublecheck if this property is picked up correctly 
or not, in the window where you are running the derbyall suite, you 
should see the derby.system.durability=test property passed as part of 
testSpecialProps for the tests..

Execute command: java -DjavaCmd=java 
-Doutputdir=C:\workghm\svnclient\trunk\test
ing\derbyall\derbylang 
-Dtopsuitedir=C:\workghm\svnclient\trunk\testing\derbyall
 -Dtopreportdir=C:\workghm\svnclient\trunk\testing\derbyall 
-Drundir=C:\workghm\
svnclient\trunk\testing 
-DtestSpecialProps=derby.debug.true=enableBtreeConsisten
cyCheck^*derby.system.durability=test*^derby.stream.error.logSeverityLevel=0 
-Dsui
tename=derbyall:derbylang -Dtopsuitename=derbyall 
org.apache.derbyTesting.functi
onTests.harness.RunTest lang/errorCode.sql

Also, you should also see the following warning in derby.log  :
"
WARNING: The database is booted with derby.system.durability=test. In 
this mode, it is possible that database may not be able to recover, 
committed transactions may be lost, database may be in an inconsistent 
state. Please use this mode only when these consequences are acceptable  "
_____________

Sunitha.

Mime
View raw message