Re: difficult design question

meislerj_at_yahoo.com wrote:

> This all seems ok logically, but it allows for the out-of-sync
> situation I described above. And, when implemented in the database, I
> have shown that I can put assignments in groups where they shouldn't
> belong. I know I can have my application handle this business
> requirement, but I'd like to model it, and have the database handle it
> if possible.

Which part of
"This can be solved by having a trigger, that checks whether an assignment already is part of a group, or work item, or by keeping track of groups/work items on assignment level (if it's NULL, you can assign them, if NOT NULL, it's prohibited)"
was misunderstood?

-- 
Regards,
Frank van Bortel

Top-posting is one way to shut me up...