[
https://issues.apache.org/jira/browse/JDO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571161#comment-13571161
]
Andy Jefferson commented on JDO-678:
------------------------------------
Hi Craig,
DataNucleus has, for a very long time, supported persistence property names
case-insensitive, due to users having hard-to-spot problems where they mistook
the cAmElCaSE sensitivity of JDO property names and got unexpected results. As
a result what 3.1.x was/is doing is just returning the lowercase form that the
property name is stored internally in. SVN trunk (3.2.x) now returns
case-sensitive names from PM.getSupportedProperties() so ought to pass any such
test. No plans to backdate this change to 3.1.x. Suggest you try with current
nightly builds (3.2.0-m4-SNAPSHOT) of "datanucleus-core", "datanucleus-api-jdo"
and "datanucleus-rdbms" (no datanucleus-enhancer or ASM needed in v3.2)
What would be a sensible move for user-friendliness (beyond the scope of this
JIRA and this release of JDO) would be for JDO to accept case-insensitive
properties. After all, is it envisaged that there will eventually be different
semantics for "javax.jdo.option.Multithreaded" and
"javax.jdo.option.multithreaded" ?
> Ability to set properties on PersistenceManager
> -----------------------------------------------
>
> Key: JDO-678
> URL: https://issues.apache.org/jira/browse/JDO-678
> Project: JDO
> Issue Type: Improvement
> Components: api, specification, tck
> Affects Versions: JDO 3 (3.0)
> Reporter: Andy Jefferson
> Assignee: Craig L Russell
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-678.patch
>
>
> It would be desirable to be able to set properties on the PersistenceManager,
> so as to be able to configure/change behaviour for a PM. Currently the PM is
> generated with particular configuration (from the PMF) and allows specific
> options to be set. But what about vendor extensions ? Having a general
> setProperty/getProperty/getSupportedProperties would be useful, and could
> also encompass the existing detachAllOnCommit, IgnoreCache, etc settings.
--
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
