You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by ch...@apache.org on 2014/01/23 17:07:56 UTC

svn commit: r1560719 - in /db/derby/docs/trunk/src/devguide: cdevcsecureprivileges.dita derbydev.ditamap

Author: chaase3
Date: Thu Jan 23 16:07:55 2014
New Revision: 1560719

URL: http://svn.apache.org/r1560719
Log:
DERBY-6431  Update Developer's Guide topic to include generated columns

Modified a Dev Guide topic and the map file.

Patch: DERBY-6431.diff

Modified:
    db/derby/docs/trunk/src/devguide/cdevcsecureprivileges.dita
    db/derby/docs/trunk/src/devguide/derbydev.ditamap

Modified: db/derby/docs/trunk/src/devguide/cdevcsecureprivileges.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/cdevcsecureprivileges.dita?rev=1560719&r1=1560718&r2=1560719&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/cdevcsecureprivileges.dita (original)
+++ db/derby/docs/trunk/src/devguide/cdevcsecureprivileges.dita Thu Jan 23 16:07:55 2014
@@ -18,17 +18,18 @@ See the License for the specific languag
 limitations under the License.
 -->
 <concept id="cdevcsecureprivileges" xml:lang="en-us">
-<title>Privileges on views, triggers, and constraints</title>
-<shortdesc>Views, triggers, and constraints operate with the privileges of the
-owner of the view, trigger, or constraint.</shortdesc>
+<title>Privileges on views, triggers, constraints, and generated columns</title>
+<shortdesc>Views, triggers, constraints, and generated columns operate with the
+privileges of the owner of the view, trigger, constraint, or generated
+column.</shortdesc>
 <prolog><metadata>
 <keywords>
-<indexterm>privileges<indexterm>on views, triggers, and constraints</indexterm></indexterm>
-<indexterm>permissions<indexterm>on views, triggers, and constraints</indexterm></indexterm>
+<indexterm>privileges<indexterm>on views, triggers, constraints, and generated columns</indexterm></indexterm>
+<indexterm>permissions<indexterm>on views, triggers, constraints, and generated columns</indexterm></indexterm>
 <indexterm>views<indexterm>privileges on</indexterm></indexterm>
 <indexterm>triggers<indexterm>privileges on</indexterm></indexterm>
-<indexterm>constraints statement<indexterm>privileges on</indexterm></indexterm>
-<indexterm>invoker rights<indexterm>versus definer rights</indexterm></indexterm>
+<indexterm>constraints<indexterm>privileges on</indexterm></indexterm>
+<indexterm>generated columns<indexterm>privileges on</indexterm></indexterm><indexterm>invoker rights<indexterm>versus definer rights</indexterm></indexterm>
 <indexterm>definer rights<indexterm>versus invoker rights</indexterm></indexterm>
 <indexterm>SQL standard authorization mode</indexterm></keywords>
 </metadata></prolog>
@@ -65,13 +66,14 @@ view <codeph>s.v</codeph>.
 determine if user <codeph>harry</codeph> has the SELECT privilege on
 <codeph>t1</codeph> or <codeph>t2</codeph>, or the EXECUTE privilege on
 <codeph>f</codeph>.</p>
-<p>Privileges on triggers and constraints work the same way as privileges on
-views. When a view, trigger, or constraint is created,
+<p>Privileges on triggers, constraints, and generated columns work the same way
+as privileges on views. When one of these objects is created,
 <ph conref="../conrefs.dita#prod/productshortname"></ph> checks that the owner
 has the required privileges. Other users do not need to have those privileges
-to perform actions on a view, trigger, or constraint.</p>
+to perform actions on a view, trigger, constraint, or generated column.</p>
 <p>If the required privileges are revoked from the owner of a view, trigger,
-or constraint, the object is dropped as part of the REVOKE statement.</p>
+constraint, or generated column, the object is dropped as part of the
+REVOKE statement.</p>
 <p>Another way of saying that privileges on objects belong to the owner is to
 call them <term>definer rights</term>, as opposed to <term>invoker rights</term>.
 This is the terminology used by the SQL standard.</p>

Modified: db/derby/docs/trunk/src/devguide/derbydev.ditamap
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/devguide/derbydev.ditamap?rev=1560719&r1=1560718&r2=1560719&view=diff
==============================================================================
--- db/derby/docs/trunk/src/devguide/derbydev.ditamap (original)
+++ db/derby/docs/trunk/src/devguide/derbydev.ditamap Thu Jan 23 16:07:55 2014
@@ -1979,7 +1979,7 @@ with updatable result sets"></topicref>
 <topicref collection-type="family" href="cdevcsecure36595.dita" navtitle="User authorizations">
 <topicref collection-type="family" href="cdevcsecure866060.dita" navtitle="Setting the SQL standard authorization mode">
 <topicref href="cdevcsecuregrantrevokeaccess.dita" navtitle="Using SQL standard authorization"></topicref>
-<topicref href="cdevcsecureprivileges.dita" navtitle="Privileges on views, triggers, and constraints"></topicref>
+<topicref href="cdevcsecureprivileges.dita" navtitle="Privileges on views, triggers, constraints, and generated columns"></topicref>
 <topicref href="cdevcsecureroles.dita" navtitle="Using SQL roles"></topicref>
 <topicref href="cdevcsecuresqlauthupgrade.dita" navtitle="Upgrading an old database to use SQL standard authorization"></topicref>
 <topicref href="rdevcsecuresqlauthexceptions.dita" navtitle="SQL standard authorization exceptions"></topicref>