| From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
|---|---|
| To: | Mike Nolan <nolan(at)gw(dot)tssi(dot)com> |
| Cc: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Alex <alex(at)meerkatsoft(dot)com>, Frank Finner <postgresql(at)finner(dot)de>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PG vs MySQL |
| Date: | 2004-03-29 04:30:24 |
| Message-ID: | 20040329002838.C51637@ganymede.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 28 Mar 2004, Mike Nolan wrote:
> The \l command should only list databases that the current user is
> authorized for, the \du command should only list users authorized for
> the current database (and perhaps only superusers should get even that
> much information), etc. Perhaps it is possible to set PG to do this,
> but that should probably be the default.
Just curious ... restricting \l itself isn't too difficult ... but how
does MySQL restrict the ability to do something like:
SELECT datname FROM pg_database;
or does it not have an equivalent to that?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Uwe C. Schroeder | 2004-03-29 04:32:56 | Re: PG vs MySQL |
| Previous Message | Marc G. Fournier | 2004-03-29 04:24:31 | Re: PG vs MySQL |