Posted by teddysnips on 12/22/05 19:43

Dan Guzman wrote:
> > So, is there any way of retaining the requirement that the
> > fldStartTimeCollectedID and the fldEndTimeCollectedID columns may not
> > contain the same value in a single row, UNLESS that value is NULL in
> > which case all is hunky dory. I should add that the clients don't much
> > care for Triggers (and neither do I for that matter).
>
> There are a couple of methods to accomplish this. One method is with a
> trigger. Another, with SQL 2000 and above, is using an index view including
> non-null values instead of a unique constraint:
[snip]

Many thanks - I'll put this to the vote just after the holidays.

I *love* usenet.

Edward

• Next in forum: intead of update/insert trigger on view question
• Prev in forum: Re: Index on two columns doesn't allow NULL in both - HELP!
• Thread view: Re: Index on two columns doesn't allow NULL in both - HELP!

[Reply to this message]