Hi Brett,
Some responses inline...
On 9/25/13 5:55 PM, Bergquist, Brett wrote:
When trying to open an existing database with the derby that I built from the
trunk I get:
ERROR XJ040: Failed to start database '/Users/brett/.netbeans-derby/csemdb'
with class loader sun.misc.Launcher$AppClassLoader@39172e08, see the next
exception for details.
ERROR XCW00: Unsupported upgrade from '10.9' to '10.11 beta'.
This is a safety mechanism to prevent someone from accidentally soft or
hard upgrading a database to the rev level of the development trunk.
There are a couple reasons that you don't want people to do this:
1) Soft-downgrade from the development trunk version may not have been
adequately tested.
2) The next major feature release will have the same major release
number as the development trunk. Since the work on that release is not
complete, upgrade trajectories are not well defined and follow-on
upgrade to the next release may not work properly.
when I connect. What do I need to do to let derby know that it is okay to
open this database (it is just a test database that can be easily rebuilt)?
You can subvert this check by specifying the following system property
when you boot the jvm:
-Dderby.database.allowPreReleaseUpgrade=true
Second question. I see an ant target called "snapshot" which I execute and it appears to build a snapshot distribution
under "releases". If I expand the ".zip" file out however, I don't see the the
"startNetworkServer" or "stopNetworkServer" scripts (I do see that Windows .bat versions but not the Unix
versions). Note I am building on OSX. Should these not be present?
Snapshots don't necessarily contain all the bits that regular releases
do. The contents of snapshots are not very well defined. It has been a
long time since the community has vetted a snapshot and the
snapshot-generating machinery may be rusty now. More information on
snapshots can be found here:
http://wiki.apache.org/db-derby/SnapshotsAndQuickBuilds
Hope this helps,
-Rick
