Differences between revisions 15 and 16
Revision 15 as of 2009-04-27 09:23:09
Size: 3891
Editor: TiagoEspinha
Comment:
Revision 16 as of 2009-09-20 22:12:04
Size: 3933
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
|| SQL Roles || [https://issues.apache.org/jira/browse/DERBY-2207 DERBY-2207] || Tiago E. || yes || Completed. Filed [https://issues.apache.org/jira/browse/DERBY-4161 DERBY-4161] for documentation clarification and [https://issues.apache.org/jira/browse/DERBY-4162 DERBY-4162] for a feature improvement. ||
|| Generated Columns || [https://issues.apache.org/jira/browse/DERBY-481 DERBY-481] || Knut A. || yes || ||
|| LOB Improvements || [https://issues.apache.org/jira/browse/DERBY-3805 DERBY-3805], [https://issues.apache.org/jira/browse/DERBY-3810 DERBY-3810], [https://issues.apache.org/jira/browse/DERBY-3907 DERBY-3907], [https://issues.apache.org/jira/browse/DERBY-3934 DERBY-3934], [https://issues.apache.org/jira/browse/DERBY-3935 DERBY-3935], [https://issues.apache.org/jira/browse/DERBY-3936 DERBY-3936], [https://issues.apache.org/jira/browse/DERBY-3970 DERBY-3970], [https://issues.apache.org/jira/browse/DERBY-3977 DERBY-3977] || || || ||
|| 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 || ||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. ||
|| OFFSET/FETCH FIRST || [https://issues.apache.org/jira/browse/DERBY-4079 DERBY-4079] || Tiago E. || yes || ||
|| standard SQL "SET" keyword in ALTER COLUMN || [https://issues.apache.org/jira/browse/DERBY-4013 DERBY-4013] || || || ||
|| 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 ||Completed. Filed and fixed [https://issues.apache.org/jira/browse/DERBY-4116 DERBY-4116]. Kim filed and fixed [https://issues.apache.org/jira/browse/DERBY-4121 DERBY-4121] for doc fixes. Filed [https://issues.apache.org/jira/browse/DERBY-4115 DERBY-4115] improvement request to allow drop statistics||
|| SQL Roles || [[https://issues.apache.org/jira/browse/DERBY-2207|DERBY-2207]] || Tiago E. || yes || Completed. Filed [[https://issues.apache.org/jira/browse/DERBY-4161|DERBY-4161]] for documentation clarification and [[https://issues.apache.org/jira/browse/DERBY-4162|DERBY-4162]] for a feature improvement. ||
|| Generated Columns || [[https://issues.apache.org/jira/browse/DERBY-481|DERBY-481]] || Knut A. || yes || ||
|| LOB Improvements || [[https://issues.apache.org/jira/browse/DERBY-3805|DERBY-3805]], [[https://issues.apache.org/jira/browse/DERBY-3810|DERBY-3810]], [[https://issues.apache.org/jira/browse/DERBY-3907|DERBY-3907]], [[https://issues.apache.org/jira/browse/DERBY-3934|DERBY-3934]], [[https://issues.apache.org/jira/browse/DERBY-3935|DERBY-3935]], [[https://issues.apache.org/jira/browse/DERBY-3936|DERBY-3936]], [[https://issues.apache.org/jira/browse/DERBY-3970|DERBY-3970]], [[https://issues.apache.org/jira/browse/DERBY-3977|DERBY-3977]] || || || ||
|| 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 || ||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. ||
|| OFFSET/FETCH FIRST || [[https://issues.apache.org/jira/browse/DERBY-4079|DERBY-4079]] || Tiago E. || yes || ||
|| standard SQL "SET" keyword in ALTER COLUMN || [[https://issues.apache.org/jira/browse/DERBY-4013|DERBY-4013]] || || || ||
|| 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 ||Completed. Filed and fixed [[https://issues.apache.org/jira/browse/DERBY-4116|DERBY-4116]]. Kim filed and fixed [[https://issues.apache.org/jira/browse/DERBY-4121|DERBY-4121]] for doc fixes. Filed [[https://issues.apache.org/jira/browse/DERBY-4115|DERBY-4115]] improvement request to allow drop statistics||

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

Members

Documentation Available

Comments

SQL Roles

DERBY-2207

Tiago E.

yes

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

Generated Columns

DERBY-481

Knut A.

yes

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

Dag

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.

OFFSET/FETCH FIRST

DERBY-4079

Tiago E.

yes

standard SQL "SET" keyword in ALTER COLUMN

DERBY-4013

In-memory back end

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

DERBY-269

Kathey

yes

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)