You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2009/09/15 22:45:59 UTC
[jira] Created: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
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
Priority: Minor
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.
[jira] Updated: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reassigned DERBY-4377:
--------------------------------
Assignee: Kim Haase
> 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
>
> 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.
[jira] Issue Comment Edited: (DERBY-4377) Developer's Guide
statement on shutting down Derby needs qualification
Posted by "Francois Orsini (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758406#action_12758406 ]
Francois Orsini edited comment on DERBY-4377 at 9/22/09 1:11 PM:
-----------------------------------------------------------------
Hi Kim,
Thanks for the prompt turnaround ;-)
Just a minor nit, sorry:
I would replace:
If you have defined Derby BUILTIN user authentication....
with:
If you have enabled Derby BUILTIN user authentication
Thanks
was (Author: forsini):
Hi Kim,
Thanks for the prompt turnaround ;-)
Just a minor nit:
I would replace:
If you have defined Derby BUILTIN user authentication....
with:
If you have enabled Derby BUILTIN user authentication
Thanks
> 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
> Attachments: DERBY-4377-2.diff, DERBY-4377.diff, 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.
[jira] Resolved: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-4377.
------------------------------
Resolution: Fixed
Issue & fix info: (was: [Patch Available])
Having heard of no issues with the revised patch, I've committed patch DERBY-4377-4.diff to the documentation trunk at revision 822457.
> 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.
[jira] Reopened: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reopened DERBY-4377:
------------------------------
Reopening because we need to improve the revised statement:
Dag.Wanvik@Sun.COM (Dag H. Wanvik) writes:
> > "Francois Orsini (JIRA)" <ji...@apache.org> writes:
> >
>> >> If you have enabled Derby's BUILTIN user authentication and created
>> >> some user at the system level (for example, by setting some username
>> >> and password in the derby.properties file), you will need to specify
>> >> credentials (e.g. username and password) in order to shut down a
>> >> Derby system.
> >
> > So if I understand this correctly; if users are defined only on the
> > database level (but BUILTIN user authentication is defined at the
> > system level), it will still be possible to shut down a Derby system
> > *without* supplying credentials?
Actually not. I tested this, and there needs to be defined at least
one user at the system level for a shutdown to work. So a more
precise wording would be:
"If you have enabled Derby's BUILTIN user authentication at the system
level (for example, by setting the property
derby.connection.requireAuthentication=true
in the derby.properties file), you will need to specify credentials
(e.g. username and password) in order to shut down a Derby system
*and* the supplied username/password must also be defined at the
system level."
> 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.diff, 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.
[jira] Updated: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4377:
-----------------------------
Attachment: tdevdvlp40464.html
DERBY-4377-4.diff
Here's yet another patch, DERBY-4377-4.diff, and the output file tdevdvlp40464.html. The patch is against the previously committed revision of the topic.
Please let me know of any needed edits.
> 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.
[jira] Resolved: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-4377.
------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
Issue & fix info: (was: [Patch Available])
Thanks for the very helpful reviews, Francois!
Committed patch DERBY-4377-3.diff to documentation trunk at revision 817850.
> 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.diff, 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.
[jira] Commented: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Francois Orsini (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758406#action_12758406 ]
Francois Orsini commented on DERBY-4377:
----------------------------------------
Hi Kim,
Thanks for the prompt turnaround ;-)
Just a minor nit:
I would replace:
If you have defined Derby BUILTIN user authentication....
with:
If you have enabled Derby BUILTIN user authentication
Thanks
> 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
> Attachments: DERBY-4377-2.diff, DERBY-4377.diff, 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.
[jira] Closed: (DERBY-4377) Developer's Guide statement on shutting
down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase closed DERBY-4377.
----------------------------
Fix appears in latest alpha manuals, so closing.
> 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.diff, 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.
[jira] Updated: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4377:
-----------------------------
Attachment: tdevdvlp40464.html
DERBY-4377-3.diff
Another good catch -- thanks, Francois. Here's another patch.
> 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
> Attachments: DERBY-4377-2.diff, DERBY-4377-3.diff, DERBY-4377.diff, 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.
Re: [jira] Commented: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by Francois Orsini <fr...@gmail.com>.
On Tue, Sep 29, 2009 at 11:33 AM, Dag H. Wanvik <Da...@sun.com> wrote:
> Dag.Wanvik@Sun.COM (Dag H. Wanvik) writes:
> >
> > So if I understand this correctly; if users are defined only on the
> > database level (but BUILTIN user authentication is defined at the
> > system level), it will still be possible to shut down a Derby system
> > *without* supplying credentials?
>
> Actually not. I tested this, and there needs to be defined at least
> one user at the system level for a shutdown to work. So a more
> precise wording would be:
>
> "If you have enabled Derby's BUILTIN user authentication at the system
> level (for example, by setting the property
>
> derby.connection.requireAuthentication=true
>
> in the derby.properties file), you will need to specify credentials
> (e.g. username and password) in order to shut down a Derby system
> *and* the supplied username/password must also be defined at the
> system level."
>
>
That works .
Re: [jira] Commented: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Dag.Wanvik@Sun.COM (Dag H. Wanvik) writes:
> "Francois Orsini (JIRA)" <ji...@apache.org> writes:
>
>> If you have enabled Derby's BUILTIN user authentication and created
>> some user at the system level (for example, by setting some username
>> and password in the derby.properties file), you will need to specify
>> credentials (e.g. username and password) in order to shut down a
>> Derby system.
>
> So if I understand this correctly; if users are defined only on the
> database level (but BUILTIN user authentication is defined at the
> system level), it will still be possible to shut down a Derby system
> *without* supplying credentials?
Actually not. I tested this, and there needs to be defined at least
one user at the system level for a shutdown to work. So a more
precise wording would be:
"If you have enabled Derby's BUILTIN user authentication at the system
level (for example, by setting the property
derby.connection.requireAuthentication=true
in the derby.properties file), you will need to specify credentials
(e.g. username and password) in order to shut down a Derby system
*and* the supplied username/password must also be defined at the
system level."
Re: [jira] Commented: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by Francois Orsini <fr...@gmail.com>.
On Tue, Sep 29, 2009 at 11:17 AM, Dag H. Wanvik <Da...@sun.com> wrote:
> "Francois Orsini (JIRA)" <ji...@apache.org> writes:
>
> > If you have enabled Derby's BUILTIN user authentication and created
> > some user at the system level (for example, by setting some username
> > and password in the derby.properties file), you will need to specify
> > credentials (e.g. username and password) in order to shut down a
> > Derby system.
>
> So if I understand this correctly; if users are defined only on the
> database level (but BUILTIN user authentication is defined at the
> system level), it will still be possible to shut down a Derby system
> *without* supplying credentials?
>
Nope - that is not what was meant.
On the contrary, if you enable authentication at the system level and don't
have any users created in derby.properties, you won't be able to shutdown a
Derby instance at all via 'jdbc:derby:;shutdown=true' (besides exiting
or/and killing the VM process). Users' credentials defined as part of a
database are not involved when shutting down a Derby instance (not a
database).
Re: [jira] Commented: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
"Francois Orsini (JIRA)" <ji...@apache.org> writes:
> If you have enabled Derby's BUILTIN user authentication and created
> some user at the system level (for example, by setting some username
> and password in the derby.properties file), you will need to specify
> credentials (e.g. username and password) in order to shut down a
> Derby system.
So if I understand this correctly; if users are defined only on the
database level (but BUILTIN user authentication is defined at the
system level), it will still be possible to shut down a Derby system
*without* supplying credentials?
[jira] Commented: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Francois Orsini (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758362#action_12758362 ]
Francois Orsini commented on DERBY-4377:
----------------------------------------
Hi Kim,
Thanks for taking care of it.
It looks good - just some minor changes to consider.
If you have enabled Derby's BUILTIN user authentication and created some user at the system level (for example, by setting some username and password in the derby.properties file), you will need to specify credentials (e.g. username and password) in order to shut down a Derby system.
> 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
> Attachments: DERBY-4377.diff, 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.
[jira] Commented: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Francois Orsini (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758431#action_12758431 ]
Francois Orsini commented on DERBY-4377:
----------------------------------------
Looks great, Kim. Thanks for taking care of it! +1
> 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
> Attachments: DERBY-4377-2.diff, DERBY-4377-3.diff, DERBY-4377.diff, 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.
[jira] Updated: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ 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
> Attachments: DERBY-4377.diff, 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.
[jira] Updated: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4377:
-----------------------------
Attachment: tdevdvlp40464.html
DERBY-4377.diff
Attaching DERBY-4377.diff and the resulting HTML file, tdevdvlp40464.html, with a proposed correction to the topic. Please let me know if any wording changes are needed here.
Thanks again to Francois for pointing out this issue.
> 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
> Attachments: DERBY-4377.diff, 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.
[jira] Updated: (DERBY-4377) Developer's Guide statement on
shutting down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-4377:
-----------------------------
Attachment: DERBY-4377-2.diff
tdevdvlp40464.html
Thanks, Francois! Here are an updated patch (DERBY-4377-2.diff) and output file that I hope incorporate your edits.
> 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
> Attachments: DERBY-4377-2.diff, DERBY-4377.diff, 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.
[jira] Closed: (DERBY-4377) Developer's Guide statement on shutting
down Derby needs qualification
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase closed DERBY-4377.
----------------------------
Fix has appeared in Latest Alpha Manuals, so closing.
> 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.