Return-Path: Delivered-To: apmail-db-derby-commits-archive@www.apache.org Received: (qmail 26577 invoked from network); 31 Mar 2005 00:27:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 Mar 2005 00:27:35 -0000 Received: (qmail 21218 invoked by uid 500); 31 Mar 2005 00:27:35 -0000 Delivered-To: apmail-db-derby-commits-archive@db.apache.org Received: (qmail 21164 invoked by uid 500); 31 Mar 2005 00:27:34 -0000 Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Derby Development" Delivered-To: mailing list derby-commits@db.apache.org Received: (qmail 21103 invoked by uid 500); 31 Mar 2005 00:27:33 -0000 Delivered-To: apmail-incubator-derby-cvs@incubator.apache.org Received: (qmail 21059 invoked by uid 99); 31 Mar 2005 00:27:33 -0000 X-ASF-Spam-Status: No, hits=-9.8 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from minotaur.apache.org (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.28) with SMTP; Wed, 30 Mar 2005 16:27:29 -0800 Received: (qmail 26465 invoked by uid 65534); 31 Mar 2005 00:27:28 -0000 Message-ID: <20050331002728.26463.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Mailer: svnmailer-1.0.0-dev Date: Thu, 31 Mar 2005 00:27:28 -0000 Subject: svn commit: r159548 [3/17] - in incubator/derby/docs/trunk/src: adminguide/ devguide/ getstart/ tuning/ To: derby-cvs@incubator.apache.org From: jta@apache.org X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Modified: incubator/derby/docs/trunk/src/adminguide/tadminovclirun.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/adminguid= e/tadminovclirun.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/adminguide/tadminovclirun.dita (original) +++ incubator/derby/docs/trunk/src/adminguide/tadminovclirun.dita Wed Mar 3= 0 16:26:36 2005 @@ -1,60 +1,60 @@ - - - - - - -Running the SimpleNetworkClientSample program - -

To connect to the Network Server that has been started as par= t -of the SimpleNetworkServerSample program:

- -Open a command prompt and change directories to the %%\demo\programs\= nserverdemo directory, -where %% is -the directory where you installed . - -Network Server clients need only the following jar files in the -CLASSPATH to connect to the Network Server. Set the CLASSPATH to include t= he -following jar files: - -The current directory (".") -db2jcc.jarThis jar file must be in your CLASSPAT= H -to use the DB2 JDBC Universal Driver. -db2jcc_license_c.jarThis jar file is the license -file for the Universal Driver for . - - - -After you have set up your environment correctly, execute the a= pplication -from the same directory: java SimpleNetworkClien= tSample -You should receive output similar to the following if the prog= ram -runs successfully: Starting Sample client program -Got a client connection via the DriverManager. -connection from datasource; getDriverName =3D=20 - IBM DB2 JDBC Universal Driver Architecture -Got a client connection via a DataSource. -Testing the connection obtained via DriverManager by executing a sample qu= ery -number of rows in sys.systables =3D 16 -Testing the connection obtained via a DataSource by executing a sample que= ry -number of rows in sys.systables =3D 16 -Goodbye! - -
-
- + + + + + + +Running the SimpleNetworkClientSample program + +

To connect to the Network Server that has been started as part +of the SimpleNetworkServerSample program:

+ +Open a command prompt and change directories to the %%\demo\programs\= nserverdemo directory, +where %% is +the directory where you installed . + +Network Server clients need only the following jar files in the +CLASSPATH to connect to the Network Server. Set the CLASSPATH to include t= he +following jar files: + +The current directory (".") +db2jcc.jarThis jar file must be in your CLASSPATH +to use the DB2 JDBC Universal Driver. +db2jcc_license_c.jarThis jar file is the license +file for the Universal Driver for . + + + +After you have set up your environment correctly, execute the a= pplication +from the same directory: java SimpleNetworkClien= tSample +You should receive output similar to the following if the prog= ram +runs successfully: Starting Sample client program +Got a client connection via the DriverManager. +connection from datasource; getDriverName =3D=20 + IBM DB2 JDBC Universal Driver Architecture +Got a client connection via a DataSource. +Testing the connection obtained via DriverManager by executing a sample qu= ery +number of rows in sys.systables =3D 16 +Testing the connection obtained via a DataSource by executing a sample que= ry +number of rows in sys.systables =3D 16 +Goodbye! + +
+
+ Propchange: incubator/derby/docs/trunk/src/adminguide/tadminovclirun.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/adminguide/tadminovnsrundemo.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/adminguid= e/tadminovnsrundemo.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/adminguide/tadminovnsrundemo.dita (origi= nal) +++ incubator/derby/docs/trunk/src/adminguide/tadminovnsrundemo.dita Wed Ma= r 30 16:26:36 2005 @@ -1,105 +1,105 @@ - - - - - -Running the NsSample sample program - -

To run the NsSample program:

- -Open a command prompt and change directories to the %%\demo\programs\ -directory, where %% -is the directory where you installed . - -Set the CLASSPATH to the current directory (".") and also inclu= de -the following jar files in order to use the Network Server and the DB2 JDB= C -Universal Driver: - -derbynet.jar

The Network Server jar file. It m= ust -be in your CLASSPATH to use any of the Network Server functions.

-
-db2jcc.jar

This jar file must be in your CLASS= PATH -to use the DB2 JDBC Universal Driver.

-db2jcc_license_c.jar

This jar file is the lice= nse -file for the Universal Driver.

-derby.jar

The database -engine jar file.

-
-
-Test the CLASSPATH settings by running the following Java comma= nd: - java org.apache.derby.tools.sysinfo -This command will show the jar -files that are in the CLASSPATH as well as the DB2 JDBC Universal Driver a= long -with their respective versions. -After you have set up your environment correctly, execute the a= pplication -from the same directory: java nserverdemo.NsSamp= le -You should receive output similar to the following if the prog= ram -runs successfully: Network Server created -Server is ready to accept connections on port 1621. -Connection number: 1. -[NsSample] Ne= twork Server started. -[NsSample] Sample <= /ph> Network Server program demo starting. -Please wait ..................... -Connection number: 2. -[NsSampleWork] Begin creating table - SAMPLETBL and necessary indexes. -[NsSampleClientThread] Thread id - 1; started. -[NsSampleWork] Thread id - 1; requests database connection,=20 - dbUrl =3Djdbc:derby:NSSampledb; -[NsSampleClientThread] Thread id - 2; started. -[NsSampleWork] Thread id - 2; requests database connection,=20 - dbUrl =3Djdbc:derby:net://localhost:1621/ - NSSampledb;create=3Dtrue:retrieveMessagesFromServerOnGetMessage=3Dtrue; - deferPrepares=3Dtrue; -Connection number: 3. -[NsSampleWork] Thread id - 1 selected 1 row [313,Derby36 ,1.7686243E23,9= 620] -[NsSampleWork] Thread id - 1 selected 1 row [313,Derby36 ,1.7686243E23,9= 620] -[NsSampleWork] Thread id - 1; deleted 1 row with t_key =3D 9620 -[NsSampleWork] Thread id - 1 selected 1 row [700,Derby34 ,8.7620301E9,95= 47] -[NsSampleWork] Thread id - 1 selected 1 row [700,Derby34 ,8.7620301E9,95= 47] -[NsSampleWork] Thread id - 2 selected 1 row [700,Derby34 ,8.7620301E9,95= 47] -[NsSampleWork] Thread id - 2 selected 1 row [700,Derby34 ,8.7620301E9,95= 47] -[NsSampleWork] Thread id - 1; inserted 1 row. -[NsSampleWork] Thread id - 1 selected 1 row [52,Derby34 ,8.7620301E9,954= 7] -[NsSampleWork] Thread id - 2; updated 1 row with t_key =3D 9547 -[NsSampleWork] Thread id - 1; deleted 1 row with t_key =3D 9547 -[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31 ,773.83636,9321= ] -[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31 ,773.83636,9321= ] -[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31 ,773.83636,9321= ] -[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31 ,773.83636,9321= ] -[NsSampleWork] Thread id - 1; inserted 1 row. -[NsSampleWork] Thread id - 2; deleted 1 row with t_key =3D 9321 -[NsSampleWork] Thread id - 1; deleted 1 row with t_key =3D 8707 -[NsSampleWork] Thread id - 1; closed connection to the database. -[NsSampleClientThread] Thread id - 1; finished all tasks. -[NsSampleWork] Thread id - 2; deleted 1 row with t_key =3D 8490 -[NsSampleWork] Thread id - 2; closed connection to the database. -[NsSampleClientThread] Thread id - 2; finished all tasks. -[NsSample] Shutting down Network Server. -Connection number: 4. -Shutdown successful. - -
-Running the NsSample program will also create the following -new directories and files:
    -
  • NSSampledb

    This directory makes up the NSSampledb database.<= /p>

  • -
  • derby.log

    This log file contains progress -and error messages.

  • -
-
-
- + + + + + +Running the NsSample sample program + +

To run the NsSample program:

+ +Open a command prompt and change directories to the %%\demo\programs\ +directory, where %% +is the directory where you installed . + +Set the CLASSPATH to the current directory (".") and also inclu= de +the following jar files in order to use the Network Server and the DB2 JDBC +Universal Driver: + +derbynet.jar

The Network Server jar file. It m= ust +be in your CLASSPATH to use any of the Network Server functions.

+
+db2jcc.jar

This jar file must be in your CLASS= PATH +to use the DB2 JDBC Universal Driver.

+db2jcc_license_c.jar

This jar file is the lice= nse +file for the Universal Driver.

+derby.jar

The database +engine jar file.

+
+
+Test the CLASSPATH settings by running the following Java comma= nd: + java org.apache.derby.tools.sysinfo +This command will show the jar +files that are in the CLASSPATH as well as the DB2 JDBC Universal Driver a= long +with their respective versions. +After you have set up your environment correctly, execute the a= pplication +from the same directory: java nserverdemo.NsSamp= le +You should receive output similar to the following if the prog= ram +runs successfully: Network Server created +Server is ready to accept connections on port 1621. +Connection number: 1. +[NsSample] Ne= twork Server started. +[NsSample] Sample <= /ph> Network Server program demo starting. +Please wait ..................... +Connection number: 2. +[NsSampleWork] Begin creating table - SAMPLETBL and necessary indexes. +[NsSampleClientThread] Thread id - 1; started. +[NsSampleWork] Thread id - 1; requests database connection,=20 + dbUrl =3Djdbc:derby:NSSampledb; +[NsSampleClientThread] Thread id - 2; started. +[NsSampleWork] Thread id - 2; requests database connection,=20 + dbUrl =3Djdbc:derby:net://localhost:1621/ + NSSampledb;create=3Dtrue:retrieveMessagesFromServerOnGetMessage=3Dtrue; + deferPrepares=3Dtrue; +Connection number: 3. +[NsSampleWork] Thread id - 1 selected 1 row [313,Derby36 ,1.7686243E23,9= 620] +[NsSampleWork] Thread id - 1 selected 1 row [313,Derby36 ,1.7686243E23,9= 620] +[NsSampleWork] Thread id - 1; deleted 1 row with t_key =3D 9620 +[NsSampleWork] Thread id - 1 selected 1 row [700,Derby34 ,8.7620301E9,95= 47] +[NsSampleWork] Thread id - 1 selected 1 row [700,Derby34 ,8.7620301E9,95= 47] +[NsSampleWork] Thread id - 2 selected 1 row [700,Derby34 ,8.7620301E9,95= 47] +[NsSampleWork] Thread id - 2 selected 1 row [700,Derby34 ,8.7620301E9,95= 47] +[NsSampleWork] Thread id - 1; inserted 1 row. +[NsSampleWork] Thread id - 1 selected 1 row [52,Derby34 ,8.7620301E9,954= 7] +[NsSampleWork] Thread id - 2; updated 1 row with t_key =3D 9547 +[NsSampleWork] Thread id - 1; deleted 1 row with t_key =3D 9547 +[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31 ,773.83636,9321] +[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31 ,773.83636,9321] +[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31 ,773.83636,9321] +[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31 ,773.83636,9321] +[NsSampleWork] Thread id - 1; inserted 1 row. +[NsSampleWork] Thread id - 2; deleted 1 row with t_key =3D 9321 +[NsSampleWork] Thread id - 1; deleted 1 row with t_key =3D 8707 +[NsSampleWork] Thread id - 1; closed connection to the database. +[NsSampleClientThread] Thread id - 1; finished all tasks. +[NsSampleWork] Thread id - 2; deleted 1 row with t_key =3D 8490 +[NsSampleWork] Thread id - 2; closed connection to the database. +[NsSampleClientThread] Thread id - 2; finished all tasks. +[NsSample] Shutting down Network Server. +Connection number: 4. +Shutdown successful. + +
+Running the NsSample program will also create the following +new directories and files:
    +
  • NSSampledb

    This directory makes up the NSSampledb database.<= /p>

  • +
  • derby.log

    This log file contains progress +and error messages.

  • +
+
+
+ Propchange: incubator/derby/docs/trunk/src/adminguide/tadminovnsrundemo.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/adminguide/tadminovrunsrvprgm.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/adminguid= e/tadminovrunsrvprgm.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/adminguide/tadminovrunsrvprgm.dita (orig= inal) +++ incubator/derby/docs/trunk/src/adminguide/tadminovrunsrvprgm.dita Wed M= ar 30 16:26:36 2005 @@ -1,74 +1,74 @@ - - - - - -Running the SimpleNetworkServerSample program - -

To run the Network -Server sample program:

- -Open a command prompt and change directories to the %%\demo\programs\= nserverdemo directory, -where %% is -the directory where you installed . - -Set the CLASSPATH to include the current directory (".") and th= e -following jar files: - -derbynet.jar

The Network Server jar file. It m= ust -be in your CLASSPATH because you start the Network Server in this program.=

-
-derby.jar

The database engine jar file.

-
-
-
-Test the CLASSPATH settings by running the following Java comma= nd: - java org.apache.derby.tools.sysinfo= -This command displays the jar -files that are in the CLASSPATH. -After you have set up your environment correctly, execute the a= pplication -from the same directory: java SimpleNetworkServ= erSample -You should receive output similar to the following if the prog= ram -runs successfully: Starting Network Server -Testing if Network Server is up and running! - Network Serve= r now running -Got an embedded connection. -Testing embedded connection by executing a sample query -number of rows in sys.systables =3D 16 -While my app is busy with embedded work, ij might connect like this: - - $ java -Dij.user=3Dme -Dij.password=3Dpw -Dij.protocol=3D - jdbc:derby:net:\\localhost:1527\ org.apache.derby.tools.ij - ij> connect 'NSSimpleDB:retrieveMessagesFromServerOnGetMessage= =3Dtrue;'; -Watch that punctuation. Put a ':' before the jcc -attributes and a ';' after each one (even the last). - - -Clients can continue to connect: -Press [Enter] to stop Server -
-

Running the SimpleNetworkServerSample program will -also create the following new directories and files:

    -
  • NSSimpleDB

    This directory makes up the NSSimpleDB database.

    -
  • derby.log

    This log file contains progress -and error messages.

  • -

-
-
- + + + + + +Running the SimpleNetworkServerSample program + +

To run the Network +Server sample program:

+ +Open a command prompt and change directories to the %%\demo\programs\= nserverdemo directory, +where %% is +the directory where you installed . + +Set the CLASSPATH to include the current directory (".") and the +following jar files: + +derbynet.jar

The Network Server jar file. It m= ust +be in your CLASSPATH because you start the Network Server in this program.=

+
+derby.jar

The database engine jar file.

+
+
+
+Test the CLASSPATH settings by running the following Java comma= nd: + java org.apache.derby.tools.sysinfo= +This command displays the jar +files that are in the CLASSPATH. +After you have set up your environment correctly, execute the a= pplication +from the same directory: java SimpleNetworkServ= erSample +You should receive output similar to the following if the prog= ram +runs successfully: Starting Network Server +Testing if Network Server is up and running! + Network Serve= r now running +Got an embedded connection. +Testing embedded connection by executing a sample query +number of rows in sys.systables =3D 16 +While my app is busy with embedded work, ij might connect like this: + + $ java -Dij.user=3Dme -Dij.password=3Dpw -Dij.protocol=3D + jdbc:derby:net:\\localhost:1527\ org.apache.derby.tools.ij + ij> connect 'NSSimpleDB:retrieveMessagesFromServerOnGetMessage= =3Dtrue;'; +Watch that punctuation. Put a ':' before the jcc +attributes and a ';' after each one (even the last). + + +Clients can continue to connect: +Press [Enter] to stop Server +
+

Running the SimpleNetworkServerSample program will +also create the following new directories and files:

    +
  • NSSimpleDB

    This directory makes up the NSSimpleDB database.

  • +
  • derby.log

    This log file contains progress +and error messages.

  • +

+
+
+ Propchange: incubator/derby/docs/trunk/src/adminguide/tadminovrunsrvprgm.di= ta ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/adminguide/tadminspace43.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/adminguid= e/tadminspace43.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/adminguide/tadminspace43.dita (original) +++ incubator/derby/docs/trunk/src/adminguide/tadminspace43.dita Wed Mar 30= 16:26:36 2005 @@ -1,48 +1,48 @@ - - - - - -Reclaiming unused space - -Compressing tables and indexes - - -

If you determine that a table and its indexes have a signific= ant -amount of unused space, use the SYSCS_UTIL.SYSCS_COMPRESS_TABLE procedure -to reclaim that space. The procedure returns the reclaimed space to the op= erating -system. By default, the SYSCS_UTIL.SYSCS_COMPRESS_TABLE procedure instruct= s to compress the t= able -and its related indexes concurrently, which can use a lot of temporary dis= k -space and memory.

-

For example, after you have determined that the FlightAvailab= ility -table and its related indexes have too much unused space, you could reclai= m -that space with the following command:

call SYSCS_UTIL.SYSCS= _COMPRESS_TABLE('APP', 'FLIGHTAVAILABILITY', 0);

The -third parameter in the SYSCS_UTIL.SYSCS_COMPRESS_TABLE() procedure determi= nes -whether the operation will run in sequential or non-sequential mode. If yo= u -specify 0 for the third argument in the procedure, the op= eration -will run in non-sequential mode. In sequential mode, compresses -the table and indexes sequentially, one at a time. Sequential compression -uses less memory and disk space but is slower. To force the operation to r= un -in sequential mode, substitute a non-zero smallint value for the third arg= ument. -The following example shows how to force the procedure to run in sequentia= l -mode:

call SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP', 'FLIGHTAVA= ILABILITY', 1);
-For more information about this command, see the . -
-
- + + + + + +Reclaiming unused space + +Compressing tables and indexes + + +

If you determine that a table and its indexes have a signific= ant +amount of unused space, use the SYSCS_UTIL.SYSCS_COMPRESS_TABLE procedure +to reclaim that space. The procedure returns the reclaimed space to the op= erating +system. By default, the SYSCS_UTIL.SYSCS_COMPRESS_TABLE procedure instruct= s to compress the t= able +and its related indexes concurrently, which can use a lot of temporary disk +space and memory.

+

For example, after you have determined that the FlightAvailab= ility +table and its related indexes have too much unused space, you could reclaim +that space with the following command:

call SYSCS_UTIL.SYSCS= _COMPRESS_TABLE('APP', 'FLIGHTAVAILABILITY', 0);

The +third parameter in the SYSCS_UTIL.SYSCS_COMPRESS_TABLE() procedure determi= nes +whether the operation will run in sequential or non-sequential mode. If you +specify 0 for the third argument in the procedure, the op= eration +will run in non-sequential mode. In sequential mode, compresses +the table and indexes sequentially, one at a time. Sequential compression +uses less memory and disk space but is slower. To force the operation to r= un +in sequential mode, substitute a non-zero smallint value for the third arg= ument. +The following example shows how to force the procedure to run in sequential +mode:

call SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP', 'FLIGHTAVA= ILABILITY', 1);
+For more information about this command, see the . +
+
+ Propchange: incubator/derby/docs/trunk/src/adminguide/tadminspace43.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/adminguide/tadmintracefacility.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/adminguid= e/tadmintracefacility.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/adminguide/tadmintracefacility.dita (ori= ginal) +++ incubator/derby/docs/trunk/src/adminguide/tadmintracefacility.dita Wed = Mar 30 16:26:36 2005 @@ -1,35 +1,35 @@ - - - - - -Controlling tracing by using the trace facility - -Network Servertrace facility -Trace facilityfor the Network Server - - - -

You will use the trace facility only if you are working with -technical support and they require the additional information provided in -this file.

-

See = for -information about managing the trace facility using the servlet interface.=

-
-
- + + + + + +Controlling tracing by using the trace facility + +Network Servertrace facility +Trace facilityfor the Network Server + + + +

You will use the trace facility only if you are working with +technical support and they require the additional information provided in +this file.

+

See = for +information about managing the trace facility using the servlet interface.=

+
+
+ Propchange: incubator/derby/docs/trunk/src/adminguide/tadmintracefacility.d= ita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/devguide/cdevadvjdbc18939.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/= cdevadvjdbc18939.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/devguide/cdevadvjdbc18939.dita (original) +++ incubator/derby/docs/trunk/src/devguide/cdevadvjdbc18939.dita Wed Mar 3= 0 16:26:36 2005 @@ -1,47 +1,47 @@ - - - - -IDEs and multiple JVMs - - - -

When you use an integrated development environment (IDE) to build a Jav= a -application, you can launch the application from within the IDE at any poi= nt -in the development process. Typically, the IDE launches a JVM dedicated to -the application. When the application completes, the JVM exits. Any databa= se -connections established by the application are closed.

-

During the development of a database application, most IDEs allow you t= o -test individual database connections and queries without running the entir= e -application. When you test an individual database connection or query (whi= ch -requires a database connection), the IDE might launch a JVM that runs in a -specialized testing environment. In this case, when a test completes, the -JVM remains active and available for further testing, and the database con= nection -established during the test remains open.

-

Because of the behaviors of the IDE described above, if you use the emb= edded JDBC -driver, you may encounter errors connecting in the following situations: -

    -
  • You test an individual query or database connection and then try to ru= n -an application that uses the same database as the tested feature. =20 -

    The -database connection established by testing the connection or query stays o= pen, -and prevents the application from establishing a connection to the same da= tabase.

  • -
  • You run an application, and before it completes (for example, while it -waits for user input), you attempt to run a second application or to test -a connection or query that uses the same database as the first application= .
  • -
-
+ + + + +IDEs and multiple JVMs + + + +

When you use an integrated development environment (IDE) to build a Java +application, you can launch the application from within the IDE at any poi= nt +in the development process. Typically, the IDE launches a JVM dedicated to +the application. When the application completes, the JVM exits. Any databa= se +connections established by the application are closed.

+

During the development of a database application, most IDEs allow you to +test individual database connections and queries without running the entire +application. When you test an individual database connection or query (whi= ch +requires a database connection), the IDE might launch a JVM that runs in a +specialized testing environment. In this case, when a test completes, the +JVM remains active and available for further testing, and the database con= nection +established during the test remains open.

+

Because of the behaviors of the IDE described above, if you use the emb= edded JDBC +driver, you may encounter errors connecting in the following situations: +

    +
  • You test an individual query or database connection and then try to run +an application that uses the same database as the tested feature. =20 +

    The +database connection established by testing the connection or query stays o= pen, +and prevents the application from establishing a connection to the same da= tabase.

  • +
  • You run an application, and before it completes (for example, while it +waits for user input), you attempt to run a second application or to test +a connection or query that uses the same database as the first application= .
  • +
+
Propchange: incubator/derby/docs/trunk/src/devguide/cdevadvjdbc18939.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/devguide/cdevadvjdbc32436.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/= cdevadvjdbc32436.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/devguide/cdevadvjdbc32436.dita (original) +++ incubator/derby/docs/trunk/src/devguide/cdevadvjdbc32436.dita Wed Mar 3= 0 16:26:36 2005 @@ -1,39 +1,39 @@ - - - - -Using Derby with IDEs - - -IDEsusing Derby withand need = to use server framework - - - - -

When you use an integrated development environment (IDE) to develop an -embedded applic= ation, you might need to run within -a server framework. This is because an IDE might try connecting to the dat= abase -from two different JVMs, whereas only a single JVM instance should connect -to a database a= t one time, as described in (multiple connections from the same JVM are allowed).

-

An "embedded = application" is one which runs in the -same JVM as the application. Such an application uses the embedded driver -(org.apache.derby.jdbc.EmbeddedDriver; see ) and connection URL (jdbc:derby:databa= seName; see )= . If you use this -driver name or connection URL from the IDE, when the IDE tries to open a s= econd connection -to the same database with the embedded , the attempt fails. Two -JVMs cannot connect to the same database in embedded mode. This situation -is described in more detail in .

-
+ + + + +Using Derby with IDEs + + +IDEsusing Derby withand need = to use server framework + + + + +

When you use an integrated development environment (IDE) to develop an +embedded applic= ation, you might need to run within +a server framework. This is because an IDE might try connecting to the dat= abase +from two different JVMs, whereas only a single JVM instance should connect +to a database a= t one time, as described in (multiple connections from the same JVM are allowed).

+

An "embedded = application" is one which runs in the +same JVM as the application. Such an application uses the embedded driver +(org.apache.derby.jdbc.EmbeddedDriver; see ) and connection URL (jdbc:derby:databa= seName; see )= . If you use this +driver name or connection URL from the IDE, when the IDE tries to open a s= econd connection +to the same database with the embedded , the attempt fails. Two +JVMs cannot connect to the same database in embedded mode. This situation +is described in more detail in .

+
Propchange: incubator/derby/docs/trunk/src/devguide/cdevadvjdbc32436.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/devguide/cdevadvjdbc35053.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/= cdevadvjdbc35053.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/devguide/cdevadvjdbc35053.dita (original) +++ incubator/derby/docs/trunk/src/devguide/cdevadvjdbc35053.dita Wed Mar 3= 0 16:26:36 2005 @@ -1,29 +1,29 @@ - - - - -Developing Tools and Using Derby with an IDE - - - -

Applications such as database tools are designed to work with databases -whose schemas and contents are unknown in advance. This chapter discusses -a few topics useful for such applications.

-
    -
  • -
-
+ + + + +Developing Tools and Using Derby with an IDE + + + +

Applications such as database tools are designed to work with databases +whose schemas and contents are unknown in advance. This chapter discusses +a few topics useful for such applications.

+
    +
  • +
+
Propchange: incubator/derby/docs/trunk/src/devguide/cdevadvjdbc35053.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/devguide/cdevadvjdbc41138.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/= cdevadvjdbc41138.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/devguide/cdevadvjdbc41138.dita (original) +++ incubator/derby/docs/trunk/src/devguide/cdevadvjdbc41138.dita Wed Mar 3= 0 16:26:36 2005 @@ -1,53 +1,53 @@ - - - - -Offering Connection Choices to the User - - -java.sql.Driver.getPropertyInfo -Available databaseslist of provided by -databaseName attribute - - - - -

JDBC's java.sql.Driver.getPropertyInfo method -allows a generic GUI tool to determine the properties for which it should -prompt a user in order to get enough information to connect to a database. -Depending on the values the user has supplied so far, additional values mi= ght -become necessary. It might be necessary to iterate though several calls to= getPropertyInfo. If no more properties are necessa= ry, -the call returns an array of zero length.

-

In a system,= do not use the method against an instance of org.apache.derby.jdbc.Embe= ddedDriver. Instead, request -the JDBC driver from the driver manager:

-java.sql.DriverManager.getDriver( - "jdbc:derby:").getPropertyInfo(URL, Prop) -

In a system,= the properties returned in the DriverPropertyInfo object are connec= tion URL attributes, including a list of booted -databases in a system (the databaseName attribute)= .

-

Databases in a system are not automatically booted until you connect wi= th -them. You can configure your system to retain the former behavior, in whic= h -case the steps described in this section will continue to work. See "de= rby.system.bootAll" in .

-

getPropertyInfo requires a connection URL and a Prope= rties object as parameters. Typically, what -you pass are values that you will use in a future call to java.= sql.DriverManager.getConnection when you actually connect -to the database. For information about setting attributes in calls to java.sql.DriverManager.getConnection, see .

-

A call to getPropertyInfo with parameters that -contain sufficient information to connect successfully returns an array of -zero length. (Receiving this zero-length array does not guarantee t= hat the getConnection call -will succeed, because something else could go wrong.)

-

Repeat calls to getPropertyInfo until it returns -a zero-length array or none of the properties remaining are desired.

-
+ + + + +Offering Connection Choices to the User + + +java.sql.Driver.getPropertyInfo +Available databaseslist of provided by +databaseName attribute + + + + +

JDBC's java.sql.Driver.getPropertyInfo method +allows a generic GUI tool to determine the properties for which it should +prompt a user in order to get enough information to connect to a database. +Depending on the values the user has supplied so far, additional values mi= ght +become necessary. It might be necessary to iterate though several calls to= getPropertyInfo. If no more properties are necessa= ry, +the call returns an array of zero length.

+

In a system,= do not use the method against an instance of org.apache.derby.jdbc.Embe= ddedDriver. Instead, request +the JDBC driver from the driver manager:

+java.sql.DriverManager.getDriver( + "jdbc:derby:").getPropertyInfo(URL, Prop) +

In a system,= the properties returned in the DriverPropertyInfo object are connec= tion URL attributes, including a list of booted +databases in a system (the databaseName attribute)= .

+

Databases in a system are not automatically booted until you connect wi= th +them. You can configure your system to retain the former behavior, in which +case the steps described in this section will continue to work. See "de= rby.system.bootAll" in .

+

getPropertyInfo requires a connection URL and a Prope= rties object as parameters. Typically, what +you pass are values that you will use in a future call to java.= sql.DriverManager.getConnection when you actually connect +to the database. For information about setting attributes in calls to java.sql.DriverManager.getConnection, see .

+

A call to getPropertyInfo with parameters that +contain sufficient information to connect successfully returns an array of +zero length. (Receiving this zero-length array does not guarantee t= hat the getConnection call +will succeed, because something else could go wrong.)

+

Repeat calls to getPropertyInfo until it returns +a zero-length array or none of the properties remaining are desired.

+
Propchange: incubator/derby/docs/trunk/src/devguide/cdevadvjdbc41138.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/devguide/cdevbabejgjd.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/= cdevbabejgjd.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/devguide/cdevbabejgjd.dita (original) +++ incubator/derby/docs/trunk/src/devguide/cdevbabejgjd.dita Wed Mar 30 16= :26:36 2005 @@ -1,30 +1,30 @@ - - - - -Granting permissions to Derby - - -Permissionsgranting to Derby - - - - -

The following section discusses which permissions should be granted to = (the -code base derby.jar).

-

See Default Policy Implementation and Policy File Syntax at http://java.sun.com/j2se/1.4.2/docs/guide/security/PolicyFiles.html<= /synph> for more information about creating policy files.

-
+ + + + +Granting permissions to Derby + + +Permissionsgranting to Derby + + + + +

The following section discusses which permissions should be granted to = (the +code base derby.jar).

+

See Default Policy Implementation and Policy File Syntax at http://java.sun.com/j2se/1.4.2/docs/guide/security/PolicyFiles.html<= /synph> for more information about creating policy files.

+
Propchange: incubator/derby/docs/trunk/src/devguide/cdevbabejgjd.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/devguide/cdevcbabejdfj.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/= cdevcbabejdfj.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/devguide/cdevcbabejdfj.dita (original) +++ incubator/derby/docs/trunk/src/devguide/cdevcbabejdfj.dita Wed Mar 30 1= 6:26:36 2005 @@ -1,38 +1,38 @@ - - - - -Running Derby under a security manager - - -Policy filesand Derby permissions -Java 2 Security Manager - - - - -

When running within an application or application server with a Java 2 -Security Manager enabled, must be granted certain permissions -to execute and access database files. Those permissions are described in "= ", below.

-

For more information about permissions and examples of creating permiss= ion -objects and granting permissions, see the Security Architecture specificat= ion -at http://java.sun.com/j2se/1.4.2/docs/guide/security/PolicyFi= les.html.

-
    -
  • -
  • -
-
+ + + + +Running Derby under a security manager + + +Policy filesand Derby permissions +Java 2 Security Manager + + + + +

When running within an application or application server with a Java 2 +Security Manager enabled, must be granted certain permissions +to execute and access database files. Those permissions are described in "= ", below.

+

For more information about permissions and examples of creating permiss= ion +objects and granting permissions, see the Security Architecture specificat= ion +at http://java.sun.com/j2se/1.4.2/docs/guide/security/PolicyFi= les.html.

+
    +
  • +
  • +
+
Propchange: incubator/derby/docs/trunk/src/devguide/cdevcbabejdfj.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts10914.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/= cdevconcepts10914.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/devguide/cdevconcepts10914.dita (origina= l) +++ incubator/derby/docs/trunk/src/devguide/cdevconcepts10914.dita Wed Mar = 30 16:26:36 2005 @@ -1,37 +1,37 @@ - - - - -Multi-user database access - - -Multi-user database accessprogramming -for - - - - -

Multi-user database access is possible if is running inside -a server framework.

-

If more than one client application tries to modify the same data, the -connection that gets the table first gets the lock on the data (either spe= cific -rows or the entire table). The second connection has to wait until the fir= st -connection commits or rolls back the transaction in order to access the da= ta. -If two connections are only querying and not modifying data, they can both -access the same data at the same time because they can each get a shared l= ock. -For more information, see .

-
+ + + + +Multi-user database access + + +Multi-user database accessprogramming +for + + + + +

Multi-user database access is possible if is running inside +a server framework.

+

If more than one client application tries to modify the same data, the +connection that gets the table first gets the lock on the data (either spe= cific +rows or the entire table). The second connection has to wait until the fir= st +connection commits or rolls back the transaction in order to access the da= ta. +If two connections are only querying and not modifying data, they can both +access the same data at the same time because they can each get a shared l= ock. +For more information, see .

+
Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts10914.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native Modified: incubator/derby/docs/trunk/src/devguide/cdevconcepts14433.dita URL: http://svn.apache.org/viewcvs/incubator/derby/docs/trunk/src/devguide/= cdevconcepts14433.dita?view=3Ddiff&r1=3D159547&r2=3D159548 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --- incubator/derby/docs/trunk/src/devguide/cdevconcepts14433.dita (origina= l) +++ incubator/derby/docs/trunk/src/devguide/cdevconcepts14433.dita Wed Mar = 30 16:26:36 2005 @@ -1,39 +1,39 @@ - - - - -Statement versus transaction runtime rollback - - -Rollbackimplicit versus explicit - - - - -

When an SQL statement generates an exception, this exception results -in a runtime rollback. A runtime rollback is a system-generated -rollback of a statement or transaction by , as opposed to an explicit rollback call from your application.

-

Extremely severe exceptions, such as disk-full errors, shut down the sy= stem, -and the transaction is rolled back when the database is next booted. Sever= e -exceptions, such as deadlock, cause transaction rollback; rolls -back all changes since the beginning of the transaction and implicitly beg= ins -a new transaction. Less severe exceptions, such as syntax errors, result i= n -statement rollback; <= /ph> rolls back only changes made by the statement -that caused the error. The application developer can insert code to explic= itly -roll back the entire transaction if desired.

-

supports par= tial rollback through the use of savepoints. See the IBM for more information.

-
+ + + + +Statement versus transaction runtime rollback + + +Rollbackimplicit versus explicit + + + + +

When an SQL statement generates an exception, this exception results +in a runtime rollback. A runtime rollback is a system-generated +rollback of a statement or transaction by , as opposed to an explicit rollback call from your application.

+

Extremely severe exceptions, such as disk-full errors, shut down the sy= stem, +and the transaction is rolled back when the database is next booted. Severe +exceptions, such as deadlock, cause transaction rollback; rolls +back all changes since the beginning of the transaction and implicitly beg= ins +a new transaction. Less severe exceptions, such as syntax errors, result in +statement rollback; <= /ph> rolls back only changes made by the statement +that caused the error. The application developer can insert code to explic= itly +roll back the entire transaction if desired.

+

supports par= tial rollback through the use of savepoints. See the IBM for more information.

+
Propchange: incubator/derby/docs/trunk/src/devguide/cdevconcepts14433.dita ---------------------------------------------------------------------------= --- svn:eol-style =3D native