> Alright,
>
> Seems the general problem is that people (me and "Benny") want to do what
> can be done with MySQL and be able to add a user, give them their own DB to
> play with, and leave it at that. However, Postgres doesn't seem to have as
> slick of a way to do such a thing because to let a user have control over
> their own database, they would have had to of been able to create the DB.
> And if they were able to create the DB, they'd be able to make others.
>
> I managed to do this (albeit not very gracefully). I created the user
> 'test' and game him permission to create DB's. Made a database with his
> username, then took away his ability to create databases. This allowed him
> to fool with his own DB (because he created it), but he could no longer
> create new DB's.
>
> Still, this seems like a bit of a crummy way to accomplish such a thing. I
> haven't been around PostgreSQL long enough to know how development takes
> place, but this is a decent feature to have in a DB I figure.
This is a valid inconvenience. Seems we should allow a createdb option
to set the database owner.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
