I'm been thinking about the derby.database.sqlAuthorization property while trying to write a JUnit test that uses GRANT/REVOKE.
Do we really need such a property to be part of the public api, it just makes Derby that little bit harder to use. Why not base the switching of the mode on the first successful execution of a GRANT statement? I also dislike the two modes, and am stil looking at ways to avoid it. Dan.
