APEX

Hi,

on another thread there was a question about what happens when a record is locked and I just did a quick test.

When I issue in a separate session a SELECT * FROM xxx WHERE abc=1 FOR UPDATE; to lock a record and then try to submit a change for this table in a form/tabular form which updates this record, APEX will just hang. I think until it get an timeout from Apache (haven't waited that long).

In a web environment wouldn't it be better that the record is first locked (the record is selected anyway to check if it has changed) and then try to update/delete it.

I know that APEX just has short running transactions, so it can't produce this types of locks, but there are also other tools around (eg Oracle*Forms) which allow to have long running transactions.

BTW, if the user stops submitting the page and tries again and tries again. This will consume each time another db connection from the mod_pls session pool and block it for usage for other users.

Thanks for considering it
Patrick
------------------------------------------------------------------------------------
Check out my APEX-blog: http://inside-apex.blogspot.com