db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ma...@apache.org
Subject svn propchange: r1133495 - svn:log
Date Fri, 10 Jun 2011 16:18:52 GMT
Author: mamta
Revision: 1133495
Modified property: svn:log

Modified: svn:log at Fri Jun 10 16:18:52 2011
------------------------------------------------------------------------------
--- svn:log (original)
+++ svn:log Fri Jun 10 16:18:52 2011
@@ -1,4 +1,6 @@
-Backporting revision 1132664 from trunk to 10.8 codeline. In addition to the backport, had
to make couple changes by hand. Added 10.7.1.1 to the list of old revisions of Derby from
which there will be upgrade to current 10.7 codeline. The reason for adding 10.7.1.1 is DERBY-5121
which caused data corruption is this release. This was fixed in the 10.7 codeline after 10.7.1.1
and we want to make sure that the faulty triggers created in 10.7.1.1 get fixed when taken
to 10.7 codeline. 
+DERBY-1482
+
+Backporting revision 1132664 from trunk to 10.7 codeline. In addition to the backport, had
to make couple changes by hand. Added 10.7.1.1 to the list of old revisions of Derby from
which there will be upgrade to current 10.7 codeline. The reason for adding 10.7.1.1 is DERBY-5121
which caused data corruption is this release. This was fixed in the 10.7 codeline after 10.7.1.1
and we want to make sure that the faulty triggers created in 10.7.1.1 get fixed when taken
to 10.7 codeline. 
 
 Also, normally, when an older release is hard upgraded to the codeline, the database can't
be booted again with the old release. But when we are testing upgrade from 10.7.1.1 to current
codeline on 10.7, we can always goback to 10.7.1.1 because it is simply a point release upgrade.
I have changed the upgrade test to allow this going back to 10.7.1.1 after the db has been
hard upgraded to 10.7 codeline.
 


Mime
View raw message