Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m inserting a row using an Oracle stored procedure which is configured to use an autonomous transaction. I’d like to insert this record, commit that transaction, and then lock the newly-inserted record so that nobody else can modify it except my current session (in another transaction, obviously, since the one that inserted it is autonomous).
How can I ensure that nobody else gets a lock on this new record before I have a chance to SELECT...FOR UPDATE it?
Using Oracle 10g.
No, you can never maintain a lock between transactions. The question you should be asking yourself is why you need to issue the commit between the
insertand theselect ... for update. The row is locked by theinsert; if you finish whatever it is that you’re doing with that row before you commit, then you don’t have to worry about re-locking the row.