Kathey Marsden wrote:
Regardless of whether we provide a mechanism allow soft upgrade, I
think that databases that have been modified by alpha software should
not be accessible by a released Derby version and thus be allowed carry
any undetected corruption with them into a supported production
environment where we really can't tell that it was the alpha software
that did the damage.
So whatever mechanism we provide to allow that should clearly
communicate that this copy of the database is never going to see a
production Derby release again.
I agree that this should be the default behavior, but I think we should
provide a mechanism that makes it possible to override this restriction.
If users are willing to take this risk, why should be prevent them for
doing so?
--
Øystein Grøvlen, Senior Staff Engineer
Sun Microsystems, Database Technology Group
Trondheim, Norway
