these are the facts:
Student [r1] is enrolled in School [r2]
Student [r3] plays Team [r4]
School [r5] manages Team [r6]
the uniqueness constraints are where you'd expect. a team is managed by just one school. a student is enrolled in just one school. a student can play on many teams.
i set up a set comparison constraint IF r3+r4 THEN r1+r6. the intent is that if a student plays on a team then that student is enrolled in the school managed by that team.
the SQL Server DLL produced doesn't enforce the constraint. it is identical DLL to that produced if the subset constraint is deleted.
do you intend to implement all constraints in the DDL or stored procedures? if not there should be a warning given.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.