30 Apr
2002
30 Apr
'02
10:19 a.m.
I think the relations table should go in the user's database. I don't
think we should get into user permissions issues. That is definitely
something MySQL should handle, not phpMyAdmin.
I'm not real familiar with the configuration scheme in phpMyAdmin, but
isn't there a way to have separate configuration options for individual
users? (So that each user can have a separate relations table?)
If it is not possible to have separate configurations per user, then the
relations table definitely belongs within each user database. (I guess it
would have to have a default name.)
Jay Davis
On Tue, Apr 30, 2002, Beck, Mike <mike.beck(a)ibmiller.de> wrote:
Unless I'm misunderstanding the question, the
appropriate
place to manage
user permissions is within MySQL. You grant select access to the
relations table for everyone, but only the administrator gets
access to
UPDATE the relations table.
this won't work for ISPs - can't see them handling the relations for a few
hundred clients databases. so there is only two possibilities:
a) have the relationstable in the users database
or
b)
for modifying the relationtable test the users rights on the table. i have
written a script to modify the relationtable (without this feature) and sent
it to marc, hope it will be in cvs as soon as he finished restructuring the
tbl_properties page (it is suppossed to be called with a link from this
page).
i think the neat way to do it would be to make this script check if a user
wants to put in links from table "a" as mastertable to test if he has e.g.
the alterpriv for table "a".
regards
mike beck
_______________________________________________
Phpmyadmin-devel mailing list
Phpmyadmin-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel