Do you have an application on the front-end that controls user access to the underlying data? If so, you might be better implementing a solution that makes use of a 'selected rows' table that holds the record ids of the rows selected, along with the user name and any pertinent datetime info. This solution has the advantage of being able to "lock" rows beyond the SQL session in which they were selected (i.e., you wouldn't need a transaction to lock them).
↧