Skip to main content

ADF Create Vs CreateInsert

Three ways in ADF to create a new row: Create, CreateInsert and CreateWithParams

As per fusion guide:

What happens when you use Create?

// create a new row for the view object
Row newRow = yourViewObject.createRow();
// mark the row as being "initialized", but not yet new
newRow.setNewRowState(Row.STATUS_INITIALIZED);

When CreateInsert is used?

It performs this additional line of code to inert the row into the row set and make it available on the iterator.
// insert the new row into the view object's default rowset
yourViewObject.insertRow(newRow);
When CreateWithParams is used?

CreateWithParams does similar tasks as CreateInsert except that it gives the feasibility to define default values declaratively for the row attributes.

Suggested usages:

      - With ADF forms you can use Create or CreateInsert.
      -  It is always safe to use CreateInsert when you have af:table as it will create a empty record and also puts it in recordset.

Transaction details:

When you create a row the transaction object associated with the current application module immediately takes note of the fact and the new entity row which gets created behind the view row is already part of the transaction's list of pending changes. As the status of new row will be marked as STATUS_INITIALIZED, it is removed from transaction's pending changes list and is considered a blank row in which the end user has not yet entered any data values. User will see the new row with default values defined on the underlying entity object. If the user never enters any data into any attribute of that initialized row, then it is as if the row never existed. When transaction is committed since the row is not part of the transaction's pending changes list, no INSERT statement will be performed and row will not be saved where as atleast one attribute in an initialized row is set, it changes the row status to STATUS_NEW and entity row is added to the transaction's list of pending changes and on commit  new row will be permanently saved.

For more brevity with an example, please refer the following link:
Thanks to Andrejus Baranovskis 

Labels:

Comments

Post a Comment

Popular posts from this blog

Spring Boot - RestTemplate PATCH request fix

  In Spring Boot, you make a simple http request as below: 1. Define RestTemplate bean @Bean public RestTemplate restTemplate () { return new RestTemplate (); } 2. Autowire RestTemplate wherever you need to make Http calls @Autowire private RestTemplate restTemplate ; 3. Use auto-wired RestTemplate to make the Http call restTemplate . exchange ( "http://localhost:8080/users" , HttpMethod . POST , httpEntity , String . class ); Above setup works fine for all Http calls except PATCH. The following exception occurs if you try to make a PATCH request as above Exception: I / O error on PATCH request for \ "http://localhost:8080/users\" : Invalid HTTP method: PATCH ; nested exception is java . net . ProtocolException : Invalid HTTP method: PATCH Cause: Above exception happens because of the HttpURLConnection used by default in Spring Boot RestTemplate which is provided by the standard JDK HTTP library. More on this at this  bug Fix: This can b...
Post a Comment
Read more

RADUS#4 - Caching the response in REST API's

  Caching in spring boot app: Caching can be used to provide a performance boost to your application users by avoiding the business logic processing involved again and again, load on your DB, requests to external systems if the users request data that's not changed frequently Different types of caching: We'll be focusing more on in-memory caching in this post i listed other options available to have an idea. In-memory caching You'll have a key-value data stores that stores the response of the request after it is served for the first time There are multiple systems like Redis, Memcached that do this distributed caching very well By default Spring provides concurrent hashmap as default cache, but you can override CacheManager to register external cache providers. Database caching Web server caching Dependencies needed: Maven < dependency > < groupId > org . springframework . boot </ groupId > < artifactId > spring - boot - starter - cache ...
Post a Comment
Read more

Settings.xml for Maven, JFrog

For development and deployment of applications we always use an artifactory in real-time world to host artifacts needed for your build and also as a target to deploy artifacts generated in the build process. For Maven, to communicate with artifactory we need a settings.xml file which is usually located at "/User/rake/.m2/settings.xml" this file consists of how to authenticate to the artifactory servers and authorizations to read/ write to different locations like release, snapshots e.t.c... Settings.xml can be generated using the artifactory you're using which in my case is JFrog , but here's a sample settings file for your reference incase you're feeling lazy☺ <?xml version="1.0" encoding="UTF-8"?> <settings xsi:schemaLocation= "http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns= "http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi= "http://www.w3.org/2001/XM...
Post a Comment
Read more