Yeah, What i am referring to is rather the "Global access options" in MySQL.
I have one "root" user with full "global access" for administration
purposes. An option would be to remove the "root" user and let every user
including the "root" user have access on table level instead of global
access.

But I fear that this would complicate administration. Each new table would
need to be assign access to the "root" user. A better solution in my
perspective is that the tables that need to be accessable on a user level
should be marked as excluded from the "global access option".

But your suggestion of removing the "root" user would solve my problem but
increase administration?.

/jonas

-----Original Message-----
From: Sergei Golubchik [mailto:[EMAIL PROTECTED]
Sent: den 18 november 2004 14:29
To: Jonas Ladenfors
Cc: Mysql (E-mail)
Subject: Re: Row level security requirements, can I still use MySQL?


Hi!

On Nov 18, Jonas Ladenfors wrote:
> Hello, I am in the position where I need row level user access, this is
> crucial in my current project. I know this has been discussed before and
the
> answer has been "use views when they become availble". But views would
still
> allow the "root" user access to the complete table, wouldnt it? I would
like
> to lock rows to certain user and not let anyone else see them, not even
the
> root user.

In MySQL there's no concept of "root" user.

If you make sure that no user on the system has select privileges on the
underlying tables, than nobody will be able to select from them.

Regards,
Sergei

--
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /   Sergei Golubchik <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, Senior Software Developer
/_/  /_/\_, /___/\___\_\___/  Osnabrueck, Germany
       <___/  www.mysql.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to