db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen" <Bernt.John...@Sun.COM>
Subject Q: Should Derby 10.3 be Derby 11?
Date Tue, 20 Feb 2007 12:24:38 GMT

I raise this question because it has now been introduced functionality
that will make Derby 10.3 not entirely compatible with 10.2.

It might seem innocent, but I think it deserves some discussion.

With the "secure by default" functionality, Rick H. has committed a
patch which requires me in my environment to start using the new
-unsecure option when a started a network server.

Consider the follwing quotes from two ongoing issues which describes
incompatible behaviour:

http://issues.apache.org/jira/browse/DERBY-2196 :
> New Default Behavior - By default, the network server now comes up
> with a Basic security policy. The customer may want to edit this
> policy, using the demo/templates/server.policy template. Among other
> side-effects, this may affect the running of customer-written
> procedures and functions as well as other parts of the application
> which run in the same VM with the engine. The customer may need to
> instrument her code to run under a SecurityManager or she may need
> to consider running with the security-disabling -unsecure option.

http://issues.apache.org/jira/browse/DERBY-2264 :
> DBA Limits - The application may need to be changed to account for
> the fact that only the Database Owner can shutdown, encrypt, and
> upgrade a database.

So, the question is then: Is this a Derby 10 release, or should it
really be Derby 11?

Myself, I have no strong feelings, but wanted to raise the discussion.

Bernt Marius Johnsen, Database Technology Group, 
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway

View raw message