This content has been marked as final. Show 2 replies
Assuming you're using an Oracle database:
That depends on whether the view's columns are updateable or not.
If they're updateable, then the database knows how to handle the update on the view, and there is nothing that you need to do additionally.
If not, then you need to create an "instead-of" trigger in the database that takes care of updating the tables instead of the view.
More information here:
How does ADF knows which rows have been changed?ADF internally keeps track of all the new or modified Entity instances. There is a way to get the list, but this is neither recommended nor necessary.
It is not possible to write in a database view?Follow Sasha's suggestions. I would add the following - if you have a non-updateble DB view but you do not want to use instead-of triggers in DB, you can override the method <tt>EntityImpl.doDML(...)</tt> which is invoked by the framework in order to persist changes. This method is documented very well, have a look at its Javadoc.