http://technology.amis.nl/2006/12/22/adf-business-components-resfresh-after-insertupdate-and-instead-of-triggers/?utm_source=rss&utm_medium=rss&utm_campaign=adf-business-components-resfresh-after-insertupdate-and-instead-of-triggers Tue, 11 Jun 2013 22:09:58 +0000 hourly 1 http://wordpress.org/?v=3.5.1 http://technology.amis.nl/2006/12/22/adf-business-components-resfresh-after-insertupdate-and-instead-of-triggers/#comment-4192 Peter Koletzke Tue, 10 Apr 2007 23:08:06 +0000 http://technology.amis.nl/blog/?p=1447#comment-4192 Thanks Lucas and Steve. That helps. To add to the content of this web page, the section Steve points to in the Developer’s Guide indicates that if you are returning a primary key value (such as one loaded by a trigger querying a sequence), you need to mark one or more attributes as a unique key so the SELECT that occurs afterwards can find the record. This technique works regardless of whether you base the primary key attribute on a DBSequence or Number. Last comment: if you have more than one INSTEAD OF trigger view entity object in your project, it might be worthwhile to create a framework class that contains this simple method. Then base all your DefImpl files on that (use the project properties setting to automate that subclassing).

]]> http://technology.amis.nl/2006/12/22/adf-business-components-resfresh-after-insertupdate-and-instead-of-triggers/#comment-4191 Steve Muench Fri, 22 Dec 2006 14:45:10 +0000 http://technology.amis.nl/blog/?p=1447#comment-4191 The same tip above holds for building entities against some complex join views as well as against synonyms for TABLE@DBLINK. Section 26.5 “Basing an Entity Object on a Join View or Remote DBLink” in the ADF Developer’s Guide for Forms/4GL Developers on the ADF Learning Center at http://www.oracle.com/technology/products/adf/learnadf.html provides some additional information.

]]>