On Sun, Sep 7, 2008 at 10:55 PM, Tom Lane <[EMAIL PROTECTED]> wrote: > Abhijit Menon-Sen <[EMAIL PROTECTED]> writes: >> (I can't help but think that the USAGE privilege is a bit unfortunate. >> If granting SELECT rights allowed currval(), INSERT allowed nextval(), >> and UPDATE allowed nextval() and setval(), then has_table_privilege() >> would have been sufficient and there would be no need to invent a new >> set of functions just to check USAGE. > > That train left the station already, and anyway you are failing to > consider "SELECT * FROM sequence", which definitely needs to have > different privileges from nextval()/currval(). >
can we tell there is consensus in create a new has_sequence_privilege()? Abhijit will you make it? if not i can make a try... -- regards, Jaime Casanova Soporte y capacitación de PostgreSQL AsesorÃa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
