Validate Attribute value at entity level validation against Runtime DB Query

On second thought, I would do it in java as a business rule. This way you are free to use pl/sql or other methods to help you implement the validation.

Using groovy limits you somewhat, e.g., you can't easily call other methods from different objects like AM or other VOs.

Timo

The rule of thumb is to install validations at the EO level. This ensures that every data written to the DB has been validated. ADF uses this approach but adds some client-side validation too (e.g. checking for numbers). Still, all data written to DB tables should be valid.

As a DBA I would enforce the final validation in the DB using constraints. In the end, users expect to see valid data in the DB and a DBA will not trust anybody but the DB.

I would implement the validation in the DB (that's the DBAs work) and on EO level.

Timo

You can do both. It depends on the use case. If the attribute can be tested without knowing other values from the same EO (or other EOs), you can do it at the attribute level. If the attribute needs information from other attributes of the same EO, it's better to do an entity-level validation. This way, you know that all attributes are given (have the values the user wants to store), and the validation must fulfill the rule.

Timo