DERBY-6162: Simplify privileged actions in NetworkServerControlApiTest

Remove calls to deprecated method java.io.File.toURL().

git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1466914 13f79535-47bb-0310-9956-ffa450edef68
DERBY-6144 nightly regression test failure, intermittent error : testStatisticsCorrectness(org.apache.derbyTesting.functionTests.tests.store.AutomaticIndexStatisticsTest)junit.framework.A

test was asserting that stats had to be created after "now".  I think the
nightly was getting a case where the time was the same.  DERBY-5046 fixed
a different part to the same test to check for greater than now, so implemented
that same fix at the offending line.  Also added some text to be printed with
the variable values if it happens again.



git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1467011 13f79535-47bb-0310-9956-ffa450edef68
DERBY-5866 (testFiringConstraintOrder(org.apache.derbyTesting.functionTests.tests.lang.TriggerTest)junit.framework.AssertionFailedError: matching triggers need to be fired in order creation:1,NO CASCADE BEFORE,DELETE,ROW)

In case of failure, this test only has information about the failing trigger. It will be good to also have a complete list of triggers in the order that they got fired. This will help figure out the intermittent test failure,

Some background information on the test
The failing test creates table T with primary key, unique key, check constraint. It creates another table TCHILD which has a foreign key reference to table T. Next, the test creates a random number of triggers on T. Triggers are one of the 12 types with various combinations of BEFORE/AFTER, INSERT/UPDATE/DELETE, ROW/STATEMENT. The trigger definition has a string associated with it which has a unique number and description of the type of trigger eg it might be '0,NO CASCADE BEFORE, DELETE, ROW', next might be '1,NO CASCADE AFTER,INSERT,STATEMENT' and so on and so forth. After the trigger creation, the test does various INSERTS/UPDATES/DELETES and for each case, it wants to test if the eligible triggers are fired in the order they were created. For instance a DELETE sql should cause all BEFORE DELETE ROW triggers to fire in the order they were created. And if the order of firing is not the order of creation, then we will run into an assertion failure error like "matching triggers need to be fired in order creation:1,NO CASCADE BEFORE,DELETE,ROW". What I find interesting though is that all the failures mentioned in this jira are for triggers created at the very begnning. For instance, jira description has the failure "matching triggers need to be fired in order creation:1,NO CASCADE BEFORE,DELETE,ROW" which means trigger number 1 got fired before I am assuming trigger number 0(provided trigger 0 is a NO CASCADE BEFORE DELETE ROW".) Another failure reported in this jira is for "0,NO CASCADE BEFORE,UPDATE,STATEMENT" but there couldn't have been another trigger created before trigger 0. 




git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1467170 13f79535-47bb-0310-9956-ffa450edef68
DERBY-6163: Reduce visibility of methods in subclasses of PageBasicOperation

Make all abstract classes in the PageBasicOperation class hierarchy
package protected. Make all constructors in the class hieararchy
package protected, except the no-argument constructors as the
Formatable interface requires them to be public.

Also reduce visibility of the RawField class, which is only used by
StoredPage in the same package.

git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1467197 13f79535-47bb-0310-9956-ffa450edef68
DERBY-6168: Clean up registered format ids

Removed the format ids for the run-time statistics classes.

git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1467200 13f79535-47bb-0310-9956-ffa450edef68
DERBY-6169: Reduce visibility of classes and methods under impl/sql

- Reduce visibility of some classes, fields and constructors under
  impl/sql/execute

- Expose InternalTriggerExecutionContext.getAutoincrementValue()
  through the interface so that callers don't have to cast the
  context to the internal implementation type

git-svn-id: https://svn.apache.org/repos/asf/db/derby/code/trunk@1467201 13f79535-47bb-0310-9956-ffa450edef68