Database constraints propagated to entity

Question

I'm trying to determine which database constraints are propagated to an entity when the entity is generated from a table.
From what I can tell, it looks like
<ul><li>primary key</li>
<li>not null</li>
<li>unique key</li>
<li>precision</li>
<li>foreign key (via
     associations)</li>
</ul>
are honored in the entity.
<ul><li>check constraints</li>
<li>default values</li>
</ul>
are not carried over.
However, even though some constraints are carried over, does this mean they are enforced (or validated)?
It looks like the following Validation rules are created:
<ul><li>Not Null constraints --&gt; Database Constraint - Mandatory</li>
<li>Precision constraints --&gt; Database Constraint - Precision</li>
</ul>
Do the rest--even the Primary Key constraint-need to be created as Validation rules in the entity? The documentation is not very clear on this.
Thanks.

Answer 1

Please read under Unique Key Validator
http://one-size-doesnt-fit-all.blogspot.com/2007/08/jdev-11g-new-features-adf-bc-entity.html
Unique Key Validator - has changed somewhat and now allows you to define validation on primary and unique keys defined for the EO (indirectly derived from the underlying table). In addition you may define multiple Unique Key Validators against the one EO where the 10.1.3 release limited this to one.
In summary the 10.1.3 release introduced the basic declarative validators against Entity Objects in ADF Business Components. Within the 11g release this has given the JDeveloper team the opportunity to go beyond the obvious validation requirements and give sophisticated declarative business rule validation still with the advantage of minimal to no coding required.