On Tue, Sep 15, 2009 at 6:42 AM, Bopolissimus Platypus Jr <[email protected]> wrote: ... > revoke all on schema public from public >
one can bypass that easily since anyone can create his own schema (by default)... so you need an addl revoke on the db side too > will do what you want but it will break a lot of other permissions, so you'd > then want to grant access to schema public selectively. i would go the opposite route; ie, revoke or completely drop the public schema. fr a security standpoint, i'd prefer deny all by default.. and fr a SQL standards pov, public schema is not even defined in the SQL standard :) kind regards -botp _________________________________________________ Kagay-Anon Linux Users' Group (KLUG) Mailing List [email protected] (http://lists.linux.org.ph/mailman/listinfo/klug) Searchable Archives: http://archives.free.net.ph
