[fdo-users] Constraints paradigm
max at geoinova.com
Tue Sep 11 05:45:28 EDT 2007
Is it possible to keep Constraints as Key/Value pairs, where Key is being
actually written in a DataStore, while associated Value gets persisted only
Generally, when speaking of Constraint list (predefined constraints on Data
Property value), approach is rather simple - i.e. list of strings ("Red",
"Green", "Blue"). Having in mind that this approach is both not storage
friendly and not localization friendly, I was thinking of implementing
following Constraint type:
Here, Data Property this Constraint is being cast upon is of type Short. Key
(0 to 3) gets persisted within DataStore, while Value exists only in
meta-model (like Attribute) and can get easily localized.
It also enables fictional UI to work upon Values part, and return associated
Key part of such Constraint. In other words, users will be still picking
"Red", "Green" or "Blue".
View this message in context: http://www.nabble.com/Constraints-paradigm-tf4421425s18162.html#a12611239
Sent from the fdo-users mailing list archive at Nabble.com.
More information about the fdo-users