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 my...@apache.org on 2007/11/12 23:50:32 UTC
svn commit: r594331 -
/db/derby/docs/branches/10.3/src/devguide/rdevcsecure125.dita
Author: myrnavl
Date: Mon Nov 12 14:50:32 2007
New Revision: 594331
URL: http://svn.apache.org/viewvc?rev=594331&view=rev
Log:
DERBY-2297 ; backport revision 594330, fixing reference to property
derby.database.readOnlyAccessUsers.
Patch by Kim Haase.
Modified:
db/derby/docs/branches/10.3/src/devguide/rdevcsecure125.dita
Modified: db/derby/docs/branches/10.3/src/devguide/rdevcsecure125.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.3/src/devguide/rdevcsecure125.dita?rev=594331&r1=594330&r2=594331&view=diff
==============================================================================
--- db/derby/docs/branches/10.3/src/devguide/rdevcsecure125.dita (original)
+++ db/derby/docs/branches/10.3/src/devguide/rdevcsecure125.dita Mon Nov 12 14:50:32 2007
@@ -63,7 +63,7 @@
'prez,cfo,numberCruncher')
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
- 'derby.database.readAccessUsers', 'clerk1,clerk2')</b></codeblock></example>
+ 'derby.database.readOnlyAccessUsers', 'clerk1,clerk2')</b></codeblock></example>
<section><p>The database administrator then requires all current users to
disconnect and re-connect. These property changes do not go into effect for
current connections. The database administrator can force current users to