db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5203) Documentation of drop=true attribute contains error
Date Mon, 02 May 2011 09:06:03 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027600#comment-13027600
] 

Knut Anders Hatlen commented on DERBY-5203:
-------------------------------------------

Thanks, Dag. I had forgotten about that. It's actually a bit more
complicated:

1) Authentication only:

- System shutdown can be performed by any user and without providing
  credentials.

- Database shutdown can be performed by any user, but credentials are
  required.

2) SQL authorization only:

- System shutdown can be performed by any user without providing
  credentials.

- Database shutdown can be performed by any user without providing
  credentials.

3) Authentication and SQL authorization:

- System shutdown requires credentials, but it can be performed by any
  user.

- Database shutdown requires credentials, and it can only be performed
  by the DBO.

For drop=true, we have this:

1) Authentication only:

- Databases can be dropped by any user, but credentials are required.

2) SQL authorization only:

- Databases can be dropped by any user without providing credentials.

3) Authentication and SQL authorization:

- Credentials are required, and only the DBO is allowed to drop the
  database.

For startMaster=true, we have this:

1) Authentication only:

- Replication can be started by any user, but credentials are
  required.

2) SQL authorization only:

- Replication can be started by any user without providing
  credentials.

3) Authentication and SQL authorization:

- Credentials are required, and only the DBO is allowed to start
  replication.

So it looks like database shutdown and drop=true follows the same
pattern as startMaster=true, whereas system shutdown breaks that
pattern.

Also, the documentation for startMaster=true is a bit inaccurate since
it implies that credentials are required if only SQL authorization is
enabled, and that only the DBO can start replication, whereas that's
only true if both authentication and SQL authorization are enabled.

I propose this new wording for all replication attributes (I think it
applies to all, but I've only tested startSlave=true and
startMaster=true), and for drop=true:

"If authentication is turned on, you must also specify this attribute
in conjunction with the user=userName and password=userPassword
attributes. If both authentication and SQL authorization are turned
on, the user must be the database owner."

For shutdown=true, we could use the same wording with the extra
qualification that it only applies to shutdown of a single database.
We would also need to mention that system shutdown requires
user=userName/password=userPassword if both authentication and SQL
authorization are enabled.

> Documentation of drop=true attribute contains error
> ---------------------------------------------------
>
>                 Key: DERBY-5203
>                 URL: https://issues.apache.org/jira/browse/DERBY-5203
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.8.1.2
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>             Fix For: 10.8.1.3, 10.9.0.0
>
>         Attachments: DERBY-5203-2.diff, DERBY-5203-2.stat, DERBY-5203-3.diff, DERBY-5203.diff,
DERBY-5203.stat, rrefattrib16471.html, rrefattribdrop.html, rrefattribdrop.html, rrefattribdrop.html
>
>
> The Reference Manual topic on the drop=true attribute, rrefattribdrop.dita, contains
the statement,
> "This attribute, like shutdown=true, cannot be combined with other attributes."
> This used to be true, but with the addition of the deregister attribute, which must be
combined with shutdown=true, it is now incorrect.
> The sentence should be changed to say only,
> "This attribute cannot be combined with other attributes."
> (I'm assuming that the deregister attribute doesn't apply to dropping an in-memory database,
since it's specific to the embedded driver. Please let me know if this isn't the case.)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message