John Embretsen wrote:
There are two types of user authorization in Derby, connection
authorization and SQL authorization. Connection authorization specifies
the access that users have to connect to a system or database."
I was (am) not sure what a system means in this context, and how that is
possibly different from a database / JDBC connection request.
That might be a doc bug, since connection authorization really only
applies to the state of a JDBC connection. I'm not sure though if a
system connection (e.g. jdbc:derby:;shutdown=true) goes through
connection authorization, I thought it was only database connections but
I could be wrong.
Dan.
