toffee wrote:
You can use a view. But you need MySQL 5.0 or later.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
net
==================
Hi all, i was wondering if its possible to do something with permissions in MySQL so that a user can only see a restricted set of data in all the tables? For example, if I have 10+ tables with data for several teams - how can i make it so that a particular team can only see data relating to them? is this maybe something that can be achieved with a UDF ? Kind regards T...
Hi all,
i was wondering if its possible to do something with permissions in MySQL so
that a user can only see a restricted set of data in all the tables?
For example, if I have 10+ tables with data for several teams - how can i
make it so that a particular team can only see data relating to them? is
this maybe something that can be achieved with a UDF ?
Kind regards
T
toffee wrote:
You can use a view. But you need MySQL 5.0 or later.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
net
==================
On Sat, 14 Oct 2006 04:59:21 +0100, "toffee" <com>
wrote:
Rescheme your data so that there is a different (set of) table/s for
each user.
Add a different MySql user for each user.
Allocate MySql table per user table permissions.
PHP script to change user/table name/s used for each logged-in user.
--
Locate your Mobile phone: <http://www.bizorg.co.uk/news.html>
Great gifts: <http://www.ThisBritain.com/ASOS_popup.html>
David Quinton wrote:
>
> Rescheme your data so that there is a different (set of) table/s for
> each user.
>
> Add a different MySql user for each user.
> Allocate MySql table per user table permissions.
> PHP script to change user/table name/s used for each logged-in user.[/ref]
In my opinion, that is a lazy (and complicated) method of doing security. There is too
much duplication, and the resulting database schema would be illogical.Not to mention
the fact that a schema change in one of these 'duplicated' tables would require applying
the schema change multiple times.
Also, your solution does not provide an elegant method of hierachical security
(operators, supervisors, managers, etc).
--
On Mon, 16 Oct 2006 08:37:29 +0000 (UTC), "Murdoc"
<com> wrote:
I agree with you. Apologies.
--
Locate your Mobile phone: <http://www.bizorg.co.uk/news.html>
Great gifts: <http://www.ThisBritain.com/ASOS_popup.html>
Bookmarks