[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-4377:
-----------------------------
Issue & fix info: [Patch Available]
> Developer's Guide statement on shutting down Derby needs qualification
> ----------------------------------------------------------------------
>
> Key: DERBY-4377
> URL: https://issues.apache.org/jira/browse/DERBY-4377
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.5.3.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Fix For: 10.6.0.0
>
> Attachments: DERBY-4377-2.diff, DERBY-4377-3.diff, DERBY-4377-4.diff, DERBY-4377.diff,
tdevdvlp40464.html, tdevdvlp40464.html, tdevdvlp40464.html, tdevdvlp40464.html
>
>
> The topic "Shutting down Derby or an individual database" (http://db.apache.org/derby/docs/dev/devguide/tdevdvlp40464.html)
begins,
> "Applications in an embedded environment shut down the Derby system by specifying the
shutdown=true attribute in the connection URL. To shut down the system, you do not specify
a database name, and you must not specify any other attribute."
> This statement actually needs some qualification, because (according to Francois Orsini)
"if you have defined Derby's BUILT-IN user authentication at the System level (e.g. setting
username / password in derby.properties file)" you do need to specify a username and password
when you shut down the database.
> The topic needs to include this information. Further suggestions on the wording are welcome.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|