security and php/postgresql

[Anon]

I'm creating (yet another) webcal for PHP using a simple postgresql database scheme. I'd like users to be able to create their own tables (calendars) and was wondering if you SQL guru types would recommend creating postgresql users or just create a user table with md5 (for example) 'encrypted' passwords. It seems to me that from an administrative point of view it would be best to use a table rather than postgresql users.

Tia,

steeve

[Anon]

I've decided to try using a 'secret' user and password in the php to access the calendar/password table. After logging into the calendar with a valid calendar/password pair the session_name() will be set equal to the calendar name. I'm hoping that this will allow a user to connect to a specific database and securly do select/update/modifiy/deletes without having to constantly check the calendar/password pair. Updates/modifies and deletes will be done only the with single 'secret' user/password as described above. This will avoid having to create new postgres users for each new calendar.

Any thoughts are welcome.

steeve