On-Lock Trigger and Releasing the Lock

Question

I have a data block which has a View as a Datasource.
I want to update some fields from that View so I use On-Lock and On-Update triggers.
In the On-Lock trigger I use a select for update nowait to lock the row.
My problem is that if I don't save the changes the lock is not released.
My problem is reproduced with the Following steps
1. Open two sessions of the form
2. Update field in one session. (The On-Lock trigger is fired)
3. Try to enter query in the Form.
4. The message Do you want to save the Changes? appears.
5. I answer No
6. I go to the second session
7. I try to update the same row and I get an error cause the Row is Locked.
Should I code another trigger? Should I issue a rollback somewhere ?
Thanks in advance.

Answer 1

Francois wrote:
Forms_ddl('ROLLBACK') will only rollback explicit SQL orders (Nothind done by Forms itself), so the risk is minimum because you lock the record when entering it then unlock it when exiting it.Is that documented anywhere? How can the Oracle database server tell the difference between row locks set by Forms automatic processing and locks expressly set by his "select for update"? Unless things have changed, a ROLLBACK removes everything... all locks, all posted changes, etc. You get a clean slate, ready to start over.
Dimitris:
I think you're going to have to re-think your application. I do not believe there is any way to unlock specific rows from one block, while preserving your uncommitted changes in others. Oracle and Forms simply do not work that way.
...unless you start setting savepoints each time the user goes in and updates a different block. Then you could potentially determine which savepoint was set, and do a rollback to savepoint. And managing that on a form with multiple updateable blocks could be a nightmare if the user bounces around from block to block making changes here and there.
It would be easier to just stop the user when he decides to enter a new query. If he has updated any other blocks, or even made changes to the block in question, then he needs to first commit, or you need to clear the entire form with a CLEAR_FORM(NO_VALIDATE,FULL_ROLLBACK);