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

>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...

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

Replies are listed 'Best First'.
Re^3: trying to understand (my)sql user rights/levels and advanced features by adrianh (Chancellor) on Sep 14, 2003 at 22:26 UTC
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.	[reply]

Replies are listed 'Best First'.

Re^3: trying to understand (my)sql user rights/levels and advanced features
by adrianh (Chancellor) on Sep 14, 2003 at 22:26 UTC

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.

[reply]