Re: Is it Possible to Enforce This Relationship at the DB Level?

On 15 oct, 22:13, dutone <dut...@xxxxxxxxxxx> wrote:
DB layout is as follows:

--------------------------------
| Client |
--------------------------------
1
|
|
0..*
-------------------------------
| Service |
-------------------------------
1
|
|
1
---------------------------------
---------------------------
| Spread*** Config | 1 ------ 1..* | Cell Config |
--------------------------------
---------------------------
1 1
| |
| |
1 |
-------------------------------- |
| Spec | |
-------------------------------- |
1 |
| |
| |
1..* |
-------------------------------- |
| Field |
1----------------------------|
--------------------------------

Every client has a spread*** that must implement a version of Spec.
For this version, the cell config must corresponding to cells in the
spread*** containing fields for the given Spec.

As long a Cell Config references a Fileld, th DB will be happy, but
the problem I have is making sure that the Fields referenced by Cell
Config are indeed children of the Spec referenced by Spread***
Config.

Is it possible to enforce this at a DB level? Maybe my model is
flawed?

Thanks

In *no case* presentation should determine design. Proper design
should be the consequence of studying sound principles of relational
modeling.

For more info...

Introduction to Database Systems. CJ Date

.

Quantcast