Re: select only user causing locks?
- From: Mladen Gogala <gogala@xxxxxxxxxxxxx>
- To: spatenau@xxxxxxxxx
- Date: Fri, 29 Apr 2005 20:16:45 +0000
On 04/29/2005 12:45:24 PM, jungwolf wrote:
> A little research with some test accounts shows that, indeed, an
> account with only select privs can issue a select for update to lock a
> row, or even a lock table x in exclusive mode. Trying to update the
> locked row obviously results in "insufficient privileges", but until
> the read-only account ends the transaction other users are unable to
> modify the row.
Oh my gawd! This reinforces my beliefs that guns should be kept locked in a=
safe place!
If you give a gun to a childish person, it will shoot itself in a foot, at =
best. This=20
is a typical case of shooting yourself in each foot, and twice, to make sur=
e that you=20
will be unable to walk!
First, you don't ever give end-lusers a tool that can issue ad-hoc queries.=
You make darned
certain that they don't have a password to connect to database even if they=
download such tool
themselves. If you catch them trying to use such a tool, make sure that the=
y will never ever
forget the experience. You are still a wolf puppy, not a young wolf. Carefu=
l with weapons.
There is a manual for new DBA people on: http://www.bofh.net. PFY, you shou=
ld learn from=20
the master.
--=20
Mladen Gogala
Oracle DBA
--
//www.freelists.org/webpage/oracle-l
Other related posts:
