[
https://issues.apache.org/jira/browse/DERBY-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270445#comment-13270445
]
Knut Anders Hatlen commented on DERBY-5442:
-------------------------------------------
> Can the derby.storage.useDefaultFilePermissions property be set on a database
> or only system-wide?
Only as a system property or as an application property in derby.properties, if
I read the code correctly.
> Also, if we say that it's dynamic but it's not a good idea to set it
> dynamically, what is the explanation for why it's not a good idea?
Since the property will only affect the permissions of files created after the
property was set, setting it dynamically will make some database files
restricted and others not restricted. One will have to shut down the database
and run operating system commands (like chmod) to change the permissions of
already created files. Although it's not a problem in itself that the
permissions are not consistent, users will typically want either all files in
the database or no files to be restricted, not a mix of restricted/unrestricted
files.
> Create documentation for restrictive file permissions feature
> -------------------------------------------------------------
>
> Key: DERBY-5442
> URL: https://issues.apache.org/jira/browse/DERBY-5442
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Dag H. Wanvik
> Assignee: Kim Haase
> Fix For: 10.9.0.0
>
> Attachments: DERBY-5442-2.diff, DERBY-5442-2.zip, DERBY-5442.diff,
> DERBY-5442.stat, DERBY-5442.zip
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
