It's only ugly to the extent that it might not produce consistent results for the records affected by lack of date/time accuracy, and to the extent that performance goes bad (for whatever reason). In other words, it might say that the status of an affected record is one thing today, and another thing toomorrow, without the status actually changing. If they can live with that, then go for it. Otherwise, plan on the trigger and a requirement to make the decision on the affected rows.