-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Nils Nordman wrote: | Hi there, | | I've got a question regarding the future upgrade path of Derby. I've | read elsewhere that one can't in-place upgrade from the cloudscape beta, | something which is understandable given the name change, etc. | | However, can I expect to be able to in-place upgrade to future versions | of Derby, if the initial databases are created by the newly checked-in | code? | | Cheers, |
Barring dramatic community decisions to the contrary, yes, you can expect to be able to in-place upgrade to future versions of Derby if the databases are created by the newly checked-in code.
When you boot derby with a new version it will perform "soft upgrade". After a soft upgrade you can still go back to your old version, but you cannot use any of the new features. if you connect with the connection attribute upgrade=true, you can use the new features but you can no longer go back to the old version.
In the past, Cloudscape has never supported in-place upgrade from a beta version even in thecases where there are not such drastic changes. Customers participating in a beta, upgrade a copy of their database to test with and don't upgrade their production database until the final version comes out.
Kathey
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3-nr1 (Windows 2000) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBLhtQG0h36bFmkocRAo1RAKCi4trRSE34Z8lFqkcdOc1mN/hgMQCfVRnZ Nktds0mal8/yoT+ajLSKFcM= =n2VA -----END PGP SIGNATURE-----
