Tom Lane wrote:
> Russell Smith <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> The entire *point* of that paragraph is that we don't have the
> >> feature.  This proposed change is surely not an improvement...
> >> 
> > Maybe removing the entire example would be more helpful.  I don't find 
> > it clear to have a command outline in a compatibility block.
> 
> True, there doesn't seem to be any point in providing a full syntax
> summary rather than just saying "the SQL spec says you can grant
> privileges on columns but we don't support that yet".

Agreed.  Patch attached and applied.  I don't see any other cases of
this in our documentation.

-- 
  Bruce Momjian  <[EMAIL PROTECTED]>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/ref/grant.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v
retrieving revision 1.64
diff -c -c -r1.64 grant.sgml
*** doc/src/sgml/ref/grant.sgml	1 Feb 2007 00:28:19 -0000	1.64
--- doc/src/sgml/ref/grant.sgml	7 Apr 2007 03:45:36 -0000
***************
*** 520,533 ****
     </para>
  
     <para>
!     The SQL standard allows setting privileges for individual columns
!     within a table:
! 
! <synopsis>
! GRANT <replaceable class="PARAMETER">privileges</replaceable>
!     ON <replaceable class="PARAMETER">table</replaceable> [ ( <replaceable class="PARAMETER">column</replaceable> [, ...] ) ] [, ...]
!     TO { PUBLIC | <replaceable class="PARAMETER">username</replaceable> [, ...] } [ WITH GRANT OPTION ]
! </synopsis>
     </para>
  
     <para>
--- 520,527 ----
     </para>
  
     <para>
!     <productname>PostgreSQL</productname> does not support the SQL-standard 
!     functionality of setting privileges for individual columns.
     </para>
  
     <para>
Index: doc/src/sgml/ref/revoke.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/ref/revoke.sgml,v
retrieving revision 1.42
diff -c -c -r1.42 revoke.sgml
*** doc/src/sgml/ref/revoke.sgml	31 Jan 2007 23:26:04 -0000	1.42
--- doc/src/sgml/ref/revoke.sgml	7 Apr 2007 03:45:37 -0000
***************
*** 231,245 ****
  
     <para>
      The compatibility notes of the <xref linkend="sql-grant" endterm="sql-grant-title"> command
!     apply analogously to <command>REVOKE</command>.  The syntax summary is:
! 
! <synopsis>
! REVOKE [ GRANT OPTION FOR ] <replaceable class="PARAMETER">privileges</replaceable>
!     ON <replaceable class="parameter">object</replaceable> [ ( <replaceable class="parameter">column</replaceable> [, ...] ) ]
!     FROM { PUBLIC | <replaceable class="parameter">username</replaceable> [, ...] }
!     { RESTRICT | CASCADE }
! </synopsis>
!     One of <literal>RESTRICT</literal> or <literal>CASCADE</literal>
      is required according to the standard, but <productname>PostgreSQL</>
      assumes <literal>RESTRICT</literal> by default.
     </para>
--- 231,238 ----
  
     <para>
      The compatibility notes of the <xref linkend="sql-grant" endterm="sql-grant-title"> command
!     apply analogously to <command>REVOKE</command>.
!     <literal>RESTRICT</literal> or <literal>CASCADE</literal>
      is required according to the standard, but <productname>PostgreSQL</>
      assumes <literal>RESTRICT</literal> by default.
     </para>
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to