[fdo-users] RE: Constraints paradigm

[Maksim Sestic]

Hi Orest,

Some time ago I've been working on a meta-model similar to FDO's. It had two
extra types of constraints and both of them turned out to be very handy:

1) Constraint based on Key/Value pair (as I explained in my previous post).
It saves storage space, speeds up queries and expressions parsing, and
solves important internationalization issues - all at once.

2) Lookup Constraint - also based on Key/Value pair, using given
Schema/Table/KeyColumn/ValueColumn (read - Class/Property) as it's data
source. This one's truly neat :-) if model has large constraint definitions
reused by many properties - e.g. street names list, administrative units
list, etc.

Regards,
Maksim Sestic 



Orest Halustchak wrote:
> 
> Hi Maksim,
> 
> 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.
> 
> Thanks,
> Orest.
> 


-- 
View this message in context: http://www.nabble.com/Constraints-paradigm-tf4421425s18162.html#a12631100
Sent from the fdo-users mailing list archive at Nabble.com.