enforcing constraints

18 Nov 2005 4:21 PM

rossu

As far as I can tell constraints like uniqueness are only enforced at the
update event. It seems more sensible to enforce them at the row or column
change event, i.e. as soon as the person inputing the info makes the mistake.
Is there a way to automatically enforce constraints on the row or column
change events?

20 Nov 2005 9:36 AM

luxspes

rossu wrote:

> As far as I can tell constraints like uniqueness are only enforced at the
> update event.

Or at the insert (or at the delete) event

It seems more sensible to enforce them at the row or column

> change event, i.e. as soon as the person inputing the info makes the mistake.

Maybe not... because the value of a field might depend on the values of
other fields (for example, if the field Status has value of "Cancelled"
then the field "DateOfCancellation" can not be null.

> Is there a way to automatically enforce constraints on the row or column
> change events?

I might not be such a good idea...
Show quote

>
>