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-6220) Provide a way for users to determine the value of a Derby property
Date Wed, 05 Jun 2013 06:26:21 GMT

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

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

If we document it with the intention of changing it later, I'd prefer we do it on the wiki
instead of the user docs, as the user docs are more normative and may lead more users into
depending on corner cases in the current property resolution.

Maybe we could also make PropertyUtil write a warning to derby.log if it finds a property
that's shadowed.

Or we could add a new property (resolved how? ;) that makes PropertyUtil write a line to derby.log
about where it took a property from, each time a property is read.
                
> 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 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

Mime
View raw message