Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.
The following page has been changed by RichardHillegas:
http://wiki.apache.org/db-derby/TenFiveOneBuddyTesting
------------------------------------------------------------------------------
|| Replication of encrypted databases || [https://issues.apache.org/jira/browse/DERBY-3890
DERBY-3890], [https://issues.apache.org/jira/browse/DERBY-3921 DERBY-3921] || Dag || || ||
|| OFFSET/FETCH FIRST || [https://issues.apache.org/jira/browse/DERBY-4079 DERBY-4079] ||
Mamta || yes || ||
|| standard SQL "SET" keyword in ALTER COLUMN || [https://issues.apache.org/jira/browse/DERBY-4013
DERBY-4013] || Mamta || || ||
- || In-memory back end || [https://issues.apache.org/jira/browse/DERBY-646 DERBY-646] ||
Rick || || ||
+ || In-memory back end || [https://issues.apache.org/jira/browse/DERBY-646 DERBY-646] ||
Rick || yes || 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|| [https://issues.apache.org/jira/browse/DERBY-269
DERBY-269] || Kathey ||yes || ||
|