db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-597) PMF : Add "readOnly" setting for better handling of read-only datastores
Date Wed, 25 Jun 2008 12:57:45 GMT

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

Andy Jefferson updated JDO-597:

    Attachment: JDOReadOnlyException.patch

Patch to add JDOReadOnlyException to "api2" project

> PMF : Add "readOnly" setting for better handling of read-only datastores
> ------------------------------------------------------------------------
>                 Key: JDO-597
>                 URL: https://issues.apache.org/jira/browse/JDO-597
>             Project: JDO
>          Issue Type: New Feature
>          Components: api2, specification
>            Reporter: Andy Jefferson
>             Fix For: JDO 2 maintenance release 2
>         Attachments: JDOReadOnlyException.patch
> A user has a datastore that is outside their control and they either don't have permission
to write to it, or maybe they have permissions but don't want to write to it. They want a
better way of handling this, preventing updates to the datastore.
> Propose :-
> PMF property (with setter/getter)
> javax.jdo.option.ReadOnly - values true | false
> JDOReadOnlyException extends JDOUserException
> Behaviour :-
> When readOnly is set to true :-
> Any operation resulting in a creation/modification of an object to be sent to the datastore
should throw a JDOReadOnlyException. This may be at commit(), flush(), or alternatively at
makePersistent() when using datastore txns, or query.deletePersistentAll(). That is, no change
should be made to the datastore contents at all.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message