adhalejr wrote:
So if I invoke EntityBase.ReadOnlyProperty = "something", what happens? Is an exception thrown?
Yes a ORMFieldIsReadonlyException exception.
It's kept with a get/set because Identity fields are also 'readonly' but have a setter because when the entity is new, they're not readonly, as you can use them then to set the PK (in adapter) so fetching the entity is easier. So to keep everything consistent, the setter is not removed.
Would there be a negative impact anywhere if the template was modified to not generate the set if a field is read-only?
No that's perfectly fine. If the field is a PK field though, be aware that you then can't set the PK field prior to fetching an entity (in adapter). If that's ok with you, no problem . (you can fetch an entity without setting the PK first, but it's a bit more verbose, e.g.: using FetchNewEntity() instead of fetch entity.