This question comes up from time to time. The answer is: yes you can, but why would you?
ie. If you're trying to avoid snapshot too old errors, then you probably just need to adjust your rollback segments to be effective for your environment. Locking the table just makes your problems worse in the long run. If you're trying to guarantee read consistency accross several queries in your script, then turn autocommit off and start a transaction at the beginning of your script and end the transaction at the end of your script. ----- Original Message ----- From: "John Gedeon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 11, 2002 12:06 PM Subject: Locking a table > Is there a way to easily lock a table ? so that no updates can happen > untill my script is done? > > I am using DBD::Oracle? > > <>< Proverbs 3:5 "Trust in the Lord with all your heart and lean not on > your own understanding;" >
