Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Sun, 19 Jul 2009 02:40:45 -0000
Message-ID: <20090719024045.4488.55261@eos.apache.org>
Subject: [Db-derby Wiki] Update of "ErandaSooriyabandara" by
 ErandaSooriyabandara

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 ErandaSooriyabandara:
http://wiki.apache.org/db-derby/ErandaSooriyabandara

------------------------------------------------------------------------------
  (https://issues.apache.org/jira/browse/DERBY-4244) crated on: 23/May/09;
  This is a issue Bryan found while we working on the DERBY-4187.
  
- === DERBY-4248 ===
- ==== convert checkConstraint.sql to JUnit ====
- (https://issues.apache.org/jira/browse/DERBY-4248) created on:25/May/09;
- 
- This is my second issue of converting test to JUNIT. As Before I convert the code using the DERBY-2151 tool. 
- I made some changes to this code considering errors while compiling and running the test. We face a problem with in "update ... where current of c1" and I create a issue on it.
- 
  I apply the patch which is modify by Bryan (java/engine/org/apache/derby/impl/sql/compile/AlterTableNode.java) to the trunk.
  After applying the patch I saw there are some of the initialized table are not there. 
  I paste the "st.executeUpdate("create table t0_1(c1 int)");" in the near above the alter table t0_1;
@@ -34, +27 @@

  It shows that the schema must change to default.
  It's happen after the connection.rollback() method used. This occurs may because of new connection crated.
  I use connection.commit() to the row-86 to keep the tables which inserted in createTestObjects() method, when rollback() method call. It successfully ran in my platform.
+ After this Bryan decided to replace the piece of code what the Knut show it as a extra codiing though it was not added a value to the code. After doing it he committed the fix, as revision 795459.
+ This is the end of this issue.
  
+ === DERBY-4248 ===
+ ==== convert checkConstraint.sql to JUnit ====
+ (https://issues.apache.org/jira/browse/DERBY-4248) created on:25/May/09;
+ 
+ This is my second issue of converting test to JUNIT. As Before I convert the code using the DERBY-2151 tool. 
+ I made some changes to this code considering errors while compiling and running the test. We face a problem with in "update ... where current of c1" and I create a issue on it.
+ 
- We think to comment the part of failure until the issue DERBY-4282 successful. So now I trying to separate the big test_checkConstraint() method into several small tests as we done on the AlterTableTest.
+ We think to comment the part of failure until the issue DERBY-4282 successful. So now I trying to separate the big test_checkConstraint() method into several small tests as we done on the AlterTableTest. 
+ I did break the code into five methods as,
+ 
+        1.testNotAllowedInCheckConstraint(),
+ 
+        2.testCheckConstriant(),
+ 
+        3.testPositionalUpdate(),
+ 
+        4.testBuiltInFunctions(),
+ 
+        5.testJira2989() 
+ 
+ And now I doing the compare the checkConstraint.out and the CheckConstraintTest for looking are there any missing parts and changes.
  
  === DERBY-4282 ===
  ==== strange behavior with the "update ... where current of c1" in the CheckConstraintTest ====