This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi guys, Another enhancement suggestion... Could you add a field configuration option to allow us to specify that an entity field is readonly - ie: the field is persisted in the DB but is not editable through the entity model. I admit this probably doesn't occur very often, but I have the situation where a reference table contains data that is updated directly in the database from outside the application. In this case, the application requires access to the data, but should not be allowed to edit it. Ideally, the designer would create a readonly field, and create only the property getter (no setter)... Cheers, Greg |
|
|
|
|
Good idea -- thanks! I've committed this and it will be included in nightly builds dated 16 Mar 2010 and above. I have called the setting Load Only rather than Read Only, to make it clear that the value is loaded from the database, but will not be persisted. |
|
|
|
