[DevExpress Support Team: CLONED FROM Q251721: How do I create a readonly property?]
Hi,
It has been 8 years, so I want to check if this is still the case.
It seems it is because I am experiencing the same issue - insert clause contains read-only property.
Since I am not comfortable writing Session descendant at current stage of application just to remove a property from insert query that never should have been there in the first place - I would like to ask if there is another way to accomplish this?
I understand private persistent fields can be used to initialize values inside object itself and persisted to database, but that can be accomplished in other ways as well - for instance creating regular property and setting UI elements as read-only.
However, putting such fields in update/insert excludes other important usage - having database generated property which we only want to show in application.
Using private persistent field exposed through public read-only property seems like a perfect fit, but unusable because those fields ends up in update/insert query which then throws database errors.
Regards,
Mario