Tim Dudgeon wrote:
OK, building from source of the 1.2 branch and applying the patch as
suggested seems to work fine.
Thanks for the suggestion.
The critical thing for me now is to ensure that databases created with
this patched version can be upgraded when a new version of derby (e.g.
10.3) comes along.
I tried opening a database created with this patched version of 10.2
with a version built form trunk, and I get this error:
Unsupported upgrade from '10.2' to '10.3 beta'.
Is this a problems with the 10.2, or the 10.3 beta?
If its with 10.2 how do I make sure the database files can be upgraded?
There is always a check to disallow upgrade to any beta release. Having
said that there is always a risk running your own fork of any derby
release in production, as the production releases may not know to
support upgrade of whatever your fork may have done to the db. The key
is determining if the changes in your fork affect any on disk
representation of the data. And of course you always have the option
of fixing the upgrade in another for fork of future releases as it is
open source.
There are development flags to allow the upgrade to the beta, search
the derby development mail list or wiki. I don't have the exact syntax.
Many thanks
Tim
Bryan Pendleton wrote:
I tried downloading the source distributions from
http://db.apache.org/derby/releases/release-10.2.1.6.cgi
Specifically I downloaded both the ".zip" and ".tar.gz" versions
of the source distributions.
When I unpacked these distributions, in both cases I got extracted
files which had "DOS" style line-end characters.
Is this expected? I had anticipated that the .zip file would have
DOS style line end characters, but the .tar.gz file would have
Unix style line end characters.
Can anybody reproduce my results?
thanks,
bryan
