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 fu...@apache.org on 2006/04/12 20:21:13 UTC

svn commit: r393563 - /db/derby/docs/trunk/src/tuning/ctunsetprop32443.dita

Author: fuzzylogic
Date: Wed Apr 12 11:21:11 2006
New Revision: 393563

URL: http://svn.apache.org/viewcvs?rev=393563&view=rev
Log:
DERBY-981: Correct inaccuracies in "Properties case study" in Tuning Guide

Committed for John Embretsen <Jo...@sun.com>

Modified:
    db/derby/docs/trunk/src/tuning/ctunsetprop32443.dita

Modified: db/derby/docs/trunk/src/tuning/ctunsetprop32443.dita
URL: http://svn.apache.org/viewcvs/db/derby/docs/trunk/src/tuning/ctunsetprop32443.dita?rev=393563&r1=393562&r2=393563&view=diff
==============================================================================
--- db/derby/docs/trunk/src/tuning/ctunsetprop32443.dita (original)
+++ db/derby/docs/trunk/src/tuning/ctunsetprop32443.dita Wed Apr 12 11:21:11 2006
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!-- 
-Copyright 1997, 2005 The Apache Software Foundation or its licensors, as applicable.  
+Copyright 1997, 2005, 2006 The Apache Software Foundation or its licensors, as applicable.  
 
 Licensed under the Apache License, Version 2.0 (the "License");  
 you may not use this file except in compliance with the License.  
@@ -46,7 +46,7 @@
 <p>You shut down and then restart your application, setting the value of <i>derby.storage.pageSize</i> to 4096 programmatically,
 as a parameter to the JVM command line:  
 <codeblock><b>java -Dderby.system.home=c:\system_directory 
-    -Dderby.storage.pageSize=4096 myApp
+    -Dderby.storage.pageSize=4096 MyApp
 CREATE TABLE anothertable (a INT, b VARCHAR(10))</b></codeblock>The page size for
 the <i>anothertable</i> table will be 4096 bytes.</p>
 <p>You establish a connection to the database and set the value of the page
@@ -65,10 +65,10 @@
 <p>You shut down the application, then restart, this time forgetting to set
 the system-wide property programmatically (as a command-line option to the
 JVM):  
-<codeblock><b>java -Dderby.system.home=c:\system_directory myApplication</b></codeblock></p>
+<codeblock><b>java -Dderby.system.home=c:\system_directory MyApp</b></codeblock></p>
 <p>You then create another table:  
 <codeblock><b>CREATE TABLE table4 (a INT, b VARCHAR(10))</b></codeblock></p>
-<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> uses the persistent database-wide property of 8192 for this
+<p><ph conref="tunconrefs.dita#prod/productshortname"></ph> uses the persistent database-wide property of 32768 for this
 table, since the database-wide property set in the previous session is persistent
 and overrides the system-wide property set in the <i>derby.properties</i> file.</p>
 <p>What you have is a situation in which three different tables each get a