in reply to trying to understand (my)sql user rights/levels and advanced features

is there some way to restrict the DB-users to just be able to modify and delete content they added to the db (from the backend side)?

MySQL allows you to control user access at the database, table and column level. See Chapter 4 of the manual for full details.

Depending on your application you might be able to use this to enable the kind of access control you want.

For example, you might create a table for each user, and only give the appropriate user insert/update permissions. You could then create a global view of all of those tables so everybody can read them.

Without some more details it's hard to tell. It might be easier to roll your own access control system.

With PostgreSQL, of course, you could add a triggers on the database side to roll your own access control system on the database side :-)

  • Comment on Re: trying to understand (my)sql user rights/levels and advanced features

Replies are listed 'Best First'.
Re: Re: trying to understand (my)sql user rights/levels and advanced features
by parasew (Beadle) on Sep 14, 2003 at 17:45 UTC
    >For example, you might create a table for each user,(..)

    hihi, that's a nice idea ;)

    but you recommended PostgreSQL and Triggers.
    as far as i found out, postgreSQL is a ORDBMS, i am wondering how to effectively use the functionality that comes with the object oriented approach such as
    inheritance

    quoting the definition of an ORDBMS:
    The main benefit to this type of database lies in the fact that the software to convert the object data between a RDBMS format and object database format is provided. Therefore it is not necessary for programmers to write code to convert between the two formats and database access is easy from an object oriented computer language.

    i was wondering if anyone has hints on how to use that functionality from the perl side...
    for example with Class::DBI...
      i am wondering how to effectively use the functionality that comes with the object oriented approach such as inheritance

      Reading the manual would seem a good starting point.

      i was wondering if anyone has hints on how to use that functionality from the perl side... for example with Class::DBI..

      Class::DBI is neutral as to the way the database represents tables, so you'd just reference the tables in the same way as normal. Whether Class::DBI is an appropriate base for your database work depends on the application.