Description:
Since we do not specify any legal way to set Read-Only properties, we have to allow the user to set them using the normal set operations.
Proposal:
Remove from 4.1.5
An SDO implementation MUST raise an error if an attempt is made to modify read-only properties (using set, unset or delete) . [COR04010509]
___________________________________
Remove the corresponding line from the table in 4.1.13
Remove the qualifier from this sentence in 4.1.7:
If the containment Property is not read-only, the delete() method MUST also remove the DataObject from its containing DataObject. [COR04010705]
_______________________________________________________
Change section 4.5.4 to
Properties can be marked as being read-only, meaning that they are not meant to be modified by client applications, but only by service providers. For example, service that retrieves objects from a database might include the object's primary key as a property
value. While a client can change the other attributes of the object, changing the value of the property representing primary key would make it impossible for the service to correctly locate the database records. It is possible that future versions of SDO will
include restrictions on how read-only properties are set.