Hi Deepa - Responses below.
On 8/9/06, Deepa Remesh (JIRA) <[email protected]> wrote:
[ http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12427035 ] Deepa Remesh commented on DERBY-1057: ------------------------------------- Hi Laura, I only went through the updates in tuning guide. Please see my comments below: 1) It would be good to add this additional info provided by Satheesh: " For new databases, there are two ways to turn on SQL authorization: 1. Set the property as a system property and then create a database. All new databases created with sqlAuthorization set as system property would automatically get this property set for them permanently. 2. Create a database first and then set the property as a *database *property. For existing databases, there is only one way to enable SQL authorization... that is by setting it as a database property. "
*** (LS) I think that this explanation should be in the documentation. I added a sentence or two to the Tuning document, but I will also add this to the Dev Guide. ...
2) This line looks out of place to me " uses the type of user authentication that is specified with the derby.authentication.provider property." ?
*** (LS) This text was provided by Mamta in an earlier comment. The text begins with "Derby users the type..." -- Laura Stewart
