Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
d845fd68
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
d845fd68
编写于
2月 15, 2012
作者:
R
Robert Haas
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
sepgsql: Reword and fix typo in docs on DML permissions.
Per report from Christoph Berg.
上级
388c2f93
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
18 addition
and
25 deletion
+18
-25
doc/src/sgml/sepgsql.sgml
doc/src/sgml/sepgsql.sgml
+18
-25
未找到文件。
doc/src/sgml/sepgsql.sgml
浏览文件 @
d845fd68
...
...
@@ -345,42 +345,35 @@ $ sudo semodule -r sepgsql-regtest
<para>
For tables, <literal>db_table:select</>, <literal>db_table:insert</>,
<literal>db_table:update</> or <literal>db_table:delete</>
is
<literal>db_table:update</> or <literal>db_table:delete</>
are
checked for all the referenced target tables depending on the kind of
statement;
in addition, <literal>db_table:select</> is also checked for
all the tables that contain the columns referenced in the
statement; in addition, <literal>db_table:select</> is also checked for
all the tables that contain columns referenced in the
<literal>WHERE</> or <literal>RETURNING</> clause, as a data source
of <literal>UPDATE</>, and so on. For example, consider:
<synopsis>
UPDATE t1 SET x = 2, y = md5sum(y) WHERE z = 100;
</synopsis>
In this case we must have <literal>db_table:select</> in addition to
<literal>db_table:update</>, because <literal>t1.a</> is referenced
within the <literal>WHERE</> clause. Column-level permissions will also be
checked for each referenced column.
for <literal>UPDATE</>, and so on.
</para>
<para>
For columns, <literal>db_column:select</> is checked on
not only the columns being read using <literal>SELECT</>, but those
being
re
ferenced in other DML statements.
Of course, it also checks <literal>db_column:update</> or
<literal>db_column:insert</> on columns being modified by
<literal>
UPDATE</> or <literal>
INSERT</>.
Column-level permissions will also be checked for each referenced column.
<literal>db_column:select</> is checked on not only the columns
being
re
ad using <literal>SELECT</>, but those being referenced in other DML
statements; <literal>db_column:update</> or <literal>db_column:insert</>
will also be checked for columns being modified by <literal>UPDATE</> or
<literal>INSERT</>.
</para>
<para>
For example, consider:
<synopsis>
UPDATE t1 SET x = 2, y = md5sum(y) WHERE z = 100;
</synopsis>
In this case, it checks <literal>db_column:update</> on the column
<literal>t1.x</> being updated, <literal>db_column:{select update}</>
on the column <literal>t1.y</> being updated and referenced, and
<literal>db_column:select</> on the column <literal>t1.z</>, since that is
only referenced in the <literal>WHERE</> clause.
Here, <literal>db_column:update</> will be checked for
<literal>t1.x</>, since it is being updated,
<literal>db_column:{select update}</> will be checked for
<literal>t1.y</>, since it is both updated and referenced, and
<literal>db_column:select</> will be checked for <literal>t1.z</>, since
it is only referenced.
<literal>db_table:{select update}</> will also be checked
at the table level.
</para>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录