Objective: Facilitate evaluation of the new features added to 10.5.

'Buddy Testing', wherein contributors test Derby 10.5 features added by other members. Each contributor is encouraged to signup for testing and providing feedback on multiple features. A single feature can also have multiple buddy testers, the more the better.

The test scenarios could be, functionality testing, integration testing, stress/load testing etc. using the newly added features in 10.5. Tests should include documentation review, both javadoc and user documentation where applicable. It would be great if any (junit) test written could be contributed back to Derby so that others can run and expand them.

Signup for testing new features in 10.5

New Feature

Link to JIRA entries


Documentation Available


SQL Roles


Tiago E.


Completed. Filed DERBY-4161 for documentation clarification and DERBY-4162 for a feature improvement.

Generated Columns


Knut A.


LOB Improvements

DERBY-3805, DERBY-3810, DERBY-3907, DERBY-3934, DERBY-3935, DERBY-3936, DERBY-3970, DERBY-3977

Replication of encrypted databases

DERBY-3890, DERBY-3921


I downloaded the "bin" bits for RC2, started and stopping replication using 2 servers on localhost following the steps in http://db.apache.org/derby/docs/dev/adminguide/cadminreplicstartrun.html and http://db.apache.org/derby/docs/dev/adminguide/cadminreplicstop.html. I verified that I was able to connect and see replicated data on the slave after stopping the replication from the master both for an unencrypted database and for an encrypted one. Found another case of DERBY-3417.



Tiago E.


standard SQL "SET" keyword in ALTER COLUMN


In-memory back end




1) Verified that in-memory db leaves no disk footprint if you set the derby.stream properties appropriately 2) Verified that VFMemoryStorageFactory.purgeDatabase( ) removes an in-memory database (primer updated). 3) Verified that you can backup an in-memory db using SYSCS_UTIL.SYSCS_BACKUP_DATABASE, remove the database from memory, then recreate it using the createFrom URL attribute 4) I increased the heap size to 512m and then began filling up a table by doubling its size with insert...select statements. I did not notice any performance difference across various page cache sizes: 2000, 1000, 500, 250, 125, and 60.

Update Statistics Stored Procedure




Completed. Filed and fixed DERBY-4116. Kim filed and fixed DERBY-4121 for doc fixes. Filed DERBY-4115 improvement request to allow drop statistics

TenFiveOneBuddyTesting (last edited 2009-09-20 22:12:04 by localhost)