From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Christoph Berg <cb(at)df7cb(dot)de> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [trivial patch] typo in doc/src/sgml/sepgsql.sgml |
Date: | 2012-02-15 14:59:50 |
Message-ID: | CA+TgmoZjUtSzHpXwwzcm4kJjwH__1AdMO3KoSbbQ+fHSCqpAKA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 15, 2012 at 5:38 AM, Christoph Berg <cb(at)df7cb(dot)de> wrote:
> diff --git a/doc/src/sgml/sepgsql.sgml b/doc/src/sgml/sepgsql.sgml
> index e45c258..ee0a255 100644
> *** a/doc/src/sgml/sepgsql.sgml
> --- b/doc/src/sgml/sepgsql.sgml
> *************** UPDATE t1 SET x = 2, y = md5sum(y) WHERE
> *** 358,364 ****
> </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.
> </para>
> --- 358,364 ----
> </synopsis>
>
> In this case we must have <literal>db_table:select</> in addition to
> ! <literal>db_table:update</>, because <literal>t1.z</> is referenced
> within the <literal>WHERE</> clause. Column-level permissions will also be
> checked for each referenced column.
> </para>
Fixed, but note that I had to recreate the patch by manual
examination. Including it inline tends to garble things.
> (It is unclear to me why the same example is cited twice here, but the
> text around them is consistent with that.)
Fixed this too, and did some related rewording and proofreading.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Kohei KaiGai | 2012-02-15 15:09:57 | Re: pgsql_fdw, FDW for PostgreSQL server |
Previous Message | Alexander Korotkov | 2012-02-15 14:40:22 | Re: Bugs/slowness inserting and indexing cubes |