Add documentation:

>>>I think a more accurate description would be "permissions not
>>>inherited by children," and that isn't necessarily a bug.
>>
>>I agree it may not be a bug - but it's more than the permissions not
>>being inherited: the parent is affected.
>
>
> Not really, once you understand what's happening.  Unless you use
> FROM ONLY, selecting from the parent selects from the parent *and*
> its children.  The parent itself isn't affected, as queries with
> FROM ONLY should demonstrate.  I understand what you're saying --
> that there's an apparent effect on the parent -- but there really
> isn't.

Sean Burlington

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index abe3b58201676df3beef25787d26b895f8088a93..f3a0129778e6d74552b940e667acec5932163ed3 100644 (file)
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Data Definition
@@ -1122,6 +1122,17 @@ SELECT name, altitude
    support this ONLY notation.
   
 
+
+
+  Inheritance and Permissions
+  
+  Because permissions are not inherited automatically a user attempting to access
+  a parent table must either have at least the same permission for the child table
+  or must use the ONLY notation. If creating a new inheritance 
+  relationship in an existing system be careful that this does not create problems.
+  
+
+  
   
    Deprecated