[fdo-users] Constraints paradigm
orest.halustchak at autodesk.com
Tue Sep 11 11:01:27 EDT 2007
FDO currently doesn't support such a constraint definition. It is
something that we've thought about but haven't had the time yet to add.
From: fdo-users-bounces at lists.osgeo.org
[mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Maksim Sestic
Sent: Tuesday, September 11, 2007 5:45 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] Constraints paradigm
Is it possible to keep Constraints as Key/Value pairs, where Key is
actually written in a DataStore, while associated Value gets persisted
Generally, when speaking of Constraint list (predefined constraints on
Property value), approach is rather simple - i.e. list of strings
"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.
(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
Key part of such Constraint. In other words, users will be still picking
"Red", "Green" or "Blue".
View this message in context:
Sent from the fdo-users mailing list archive at Nabble.com.
fdo-users mailing list
fdo-users at lists.osgeo.org
More information about the fdo-users