Free reverse phone lookup canada

I talked about some use case which calls for Primary Key update from UI and their solutions long back in one of my old post http://www.jobinesh.com/2009/06/target-unreachable-identifier-row.html.  This post is in continuation of the same discussion. Good news is that the 11.1.2.0.0 release of ADF started supporting a specific use case that involves PK change. To make it clear, ADF out of the box supports/handles the scenario in which your entity objects primary key attribute is populated by database trigger when you post the newly created row(or any PK changes during postChanges operation,  while committing a transaction). To leverage this support, you may want to keep Refresh on Update or Refresh on Insert flags (as appropaite) to " true" for the Primary Key attributes (which get updated during posting changes to DB) in the entity object. Note that ADF (ADF Faces when used along with ADF binding and Business Components) officially does not support(not certified) any kind of primary key update from UI(ADF Faces). If you see a reason for allowing user to update Key attributes from UI, then always use Surrogate Key approach, which can be enabled through DB Sequence.

Note that, in the above post Im talking about updating primary keys from UI(where update from UI reaches underlying entity object through ADF binding layer).  To clarify, PK update support at business component level is available since 11.1.2.0.0, however same through UI (which is bound to business components through ADF binding) is not certified.