Re: Why sequence grant is separated from table?
От | Szymon Guz |
---|---|
Тема | Re: Why sequence grant is separated from table? |
Дата | |
Msg-id | CAFjNrYvWZYDZu7Dd7Hhemp1fY+YCKdA2a=8aU1A_KW-4N-eH_w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Why sequence grant is separated from table? (Rural Hunter <ruralhunter@gmail.com>) |
Список | pgsql-admin |
On 19 June 2013 12:06, Rural Hunter <ruralhunter@gmail.com> wrote:
于 2013/6/19 17:47, Szymon Guz 写道:oh, is it possible to separately grant nextval and setval on sequence currently?On 19 June 2013 11:35, Rural Hunter <ruralhunter@gmail.com> wrote:I really hate the error "permission denied for sequence xxxxx" when I grant on a table but forget to grant additionally on the related sequence to users. Can the permission of table and related sequences be merged?I can imagine a situation where you want a user to be granted rights on a table, to use sequence with curval and nextval functions, but not setval, as it can provide some database problems.
- SELECT
- For sequences, this privilege also allows the use of the
currval
function. - For sequences, this privilege also allows the use of the
- UPDATE
- For sequences, this privilege allows the use of the
nextval
andsetval
functions. - For sequences, this privilege allows the use of the
Can we get it from the column definition such as a serial column?What's more, in general, you cannot say which sequence is used for which table, if the sequence is not owned by the table.
Sure we can.
At least granting insert on a table means to grant update on the sequence used by serial columns.Which permissions of a table do you want to merge with which permissions of sequences?
It could be done. Unfortunately it doesn't cover all cases, like some ORMs which can use one sequence for many different tables, but of course for serials it can be done.
Szymon
В списке pgsql-admin по дате отправления: