Thanks
Aswath Rao

My general directive is that check constraints protect your data from programmer error. Anything which is true about your data should be embedded in the database as a constraint if possible. This makes the check constraint the default choice until you discover that it causes optimisation problems that you can’t work around. (Or can only find workarounds that produce problems that are worse than the problem you’re trying to solve).

Do you recommend creating the column constraint date_col = trunc(date_col) for all date columns if you planning to use them in your query as a predicate? Or we need to use the column constraint date_col = trunc(date_col) only if we see performance issues due to this issue?

Thanks
Aswath Rao