[ 
https://issues.apache.org/jira/browse/DERBY-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rick Hillegas updated DERBY-6220:
---------------------------------

    Attachment: derby-6220-02-ab-newSystemFunction.diff

Attaching derby-6220-02-ab-newSystemFunction.diff. This patch adds an upgrade 
test and a permissions test for the new system function.

Thanks for that feedback, Dag and Knut. I'm going to stop work on this issue. 
Hopefully this analysis and patch will be useful if someone wants to tackle the 
complete solution. I do not plan to do any more work on this issue but I will 
leave the issue open.

Touches the following additional files:

M       
java/testing/org/apache/derbyTesting/functionTests/tests/lang/DBOAccessTest.java
A       
java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/Changes10_11.java
M       
java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/UpgradeRun.java

                
> Provide a way for users to determine the value of a Derby property
> ------------------------------------------------------------------
>
>                 Key: DERBY-6220
>                 URL: https://issues.apache.org/jira/browse/DERBY-6220
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>         Attachments: derby-6220-01-aa-cleanupProperty.diff, 
> derby-6220-01-aa-newSystemFunction.diff, 
> derby-6220-02-ab-newSystemFunction.diff
>
>
> Derby properties can be specified as system properties, values stored in 
> derby.properties, and values stored in the database via the 
> syscs_set_database_property procedure. The rules for how these property sets 
> interact are confusing. It would be good to provide users a way to figure out 
> what Derby thinks a property is set to. Maybe we could provide a builtin or 
> system function for this purpose.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to