[JDO-597] PMF : Add "readOnly" setting for better handling of read-only datastores

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: JDO 2 maintenance release 2 (2.2)
• Component/s: api, api2-legacy, specification
• Assignee: Andy Jefferson
• Reporter: Andy Jefferson
• Created: 23/Jun/08 07:20
• Updated: 14/Jun/10 11:02
• Resolved: 15/Aug/08 22:55

Description

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.