Re: Alternative to Select in table check constraint

> This is more of an implementation option, but when I worry about what is
> active/inactive I put start/end dates on the tables. Then you don't need
> active indicators. You just look for the record where now() is >= start
> date and now() <= end date or end date is null. You can even
> activate/deactivate a badge on a future date. Of course, this complicates
> the data integrity - you will need some kind of specialized trigger that
> checks the data and makes sure there are no date overlaps to ensure you
> don't have two badges active at the same time. But is also gives you a
> history of badges and their activities.

Good point. I take it that this type of solution stems from temporal schema design.

Regards,

Richard Broersma Jr.