Yes, WAIT N does tell how long should you wait to obtain a lock on a row that is currently locked by some other transaction, you can not use it to limit for how long you should keep the lock on a row.
Nevertheless, it is a very strange requirenment to limit the time in which a particular transaction should execute and to roll it back if this time is exceeded. I think the closest think to meet this requirement would be to limit the CPU_PER_CALL in the calling user's profile. And yes, I know it is not the same, it is just the closest thing I could think of.
Jurij Modic
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Bookmarks