db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhille...@apache.org
Subject svn commit: r1807935 - in /db/derby/site/trunk/src/documentation/content/xdocs: derby_charter.xml derby_downloads.xml faq.xml index.xml license.xml
Date Sat, 09 Sep 2017 23:45:38 GMT
Author: rhillegas
Date: Sat Sep  9 23:45:38 2017
New Revision: 1807935

URL: http://svn.apache.org/viewvc?rev=1807935&view=rev
DERBY-6941: Re-organize downloads page in order to highlight which Java versions support which
Derby releases.


Modified: db/derby/site/trunk/src/documentation/content/xdocs/derby_charter.xml
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/derby_charter.xml?rev=1807935&r1=1807934&r2=1807935&view=diff
--- db/derby/site/trunk/src/documentation/content/xdocs/derby_charter.xml (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/derby_charter.xml Sat Sep  9 23:45:38
@@ -39,14 +39,14 @@ The Derby project develops open source d
   Database technology is defined as software that processes data related 
   requests from applications. 
-  Data requests include data definition, data modification and data retrieval.
-  Database GUI tooling and IDEs are not developed by the Derby project.
+  Data requests include data definition, data modification, and data retrieval.
+  The Derby project does not develop database GUI tools or IDEs.
   <section><title>Pure Java</title>
-  Derby technology is written in Java to take advantage of Java’s write 
+  Derby technology is written in Java in order to take advantage of Java’s write 
   once, run anywhere promise. 
   Java platforms such as OSGi, J2ME, J2SE and J2EE are supported as appropriate.
@@ -54,29 +54,28 @@ The Derby project develops open source d
   <section><title>Easy to Use</title>
-  Derby technology aims to be easy to use for software developers and zero administration
for end users.
+  Derby intends to be easy for software developers to use and to impose no administrative
burden on end users.
   <section><title>Small Footprint</title>
-  Derby technologies are designed to provide significant useful 
-  functionality in a small code size footprint with efficient runtime 
-  resource usage.
+  Derby provides significant
+  functionality, fits in a small code size footprint, and uses runtime 
+  resources efficiently.
   <section><title>Standards based</title>
-  Derby technology adheres to database standards such as JDBC
-  and ANSI SQL standards.
-  This means Derby provides the functionality expected of a modern relational
-  database, 
+  Derby adheres to database standards such as JDBC
+  and the ANSI/ISO SQL specification.
+  This means that Derby provides modern relational
+  database functionality, 
   including SQL syntax, transaction management, concurrency, triggers, 
   and online backups.
-  And it also means developers can later migrate to other databases if they
-  so choose.
+  It also means that developers can migrate easily to other databases later on.
@@ -84,11 +83,11 @@ The Derby project develops open source d
-  Derby technology provides secure data management appropriate to environment 
-  the engine is executing in. Traditional enterprise database systems rely on 
-  the machine being physically protected (locked machine room) for security, 
-  Derby databases are often in unprotected environments, such as laptops and 
-  unattended hardware.
+  Derby provides secure data management appropriate to the environment 
+  where the engine runs. While traditional enterprise database systems rely on 
+  machines being physically isolated in a locked room, 
+  Derby databases often reside on unprotected laptops and 
+  other unattended hardware.
@@ -98,31 +97,29 @@ The Derby project develops open source d
   <section><title>Derby embedded database engine</title>
-   The core of the technology, Derby’s database engine is a full 
-   functioned relational embedded database engine. JDBC and SQL are the 
-   programming APIs. 
+   The core Derby technology is a fully functional, embedded database engine.
+   The engine can be programmed using SQL over JDBC. 
   <section><title>Derby network server</title>
-   The Derby network server increases the reach of the Derby database
-   engine by providing traditional client server functionality. 
-   The network server allows clients to connect over TCP/IP using the standard 
+   The Derby network server provides traditional client/server access to the Derby engine.
+   The network server lets clients connect over TCP/IP using a subset of the
    DRDA protocol. 
-   The network server allows the Derby engine to support networked JDBC, 
-   ODBC/CLI, Perl and PHP.
+   The network server supports connections from networked JDBC, 
+   ODBC/CLI, Perl, and PHP clients.
   <section><title>Database Utilities</title>
    <li> <code>ij</code> -- a tool that allows SQL scripts to be executed
-        against any JDBC database.
+        against any JDBC database, including non-Derby databases.
-   <li> <code>dblook</code> -- Schema extraction tool for a Derby database.
+   <li> <code>dblook</code> -- a schema extraction tool for a Derby database.
-   <li> <code>sysinfo</code> -- Utility to display version numbers and
+   <li> <code>sysinfo</code> -- a utility to display version numbers and
         class path.
@@ -133,26 +130,25 @@ The Derby project develops open source d
 <section><title>Derby History</title>
-Cloudscape Inc, an Oakland, California start-up, was founded in 1996 to 
-develop Java database technology. The first release of the database engine, 
-then called JBMS, was in 1997. 
-Subsequently the product was renamed Cloudscape and releases were made about 
-every six months. 
-In 1999 Informix Software, Inc., acquired Cloudscape, Inc. 
-In 2001 IBM acquired the database assets of Informix Software, 
+In 1996, a start-up called Cloudscape Inc. was founded in Oakland, California in order to
+develop Java database technology. In 1997, Cloudscape released the first version of its database
+then called JBMS. 
+Subsequently, the product was renamed as Cloudscape and the company adopted a six month release
+In 1999, Informix Software, Inc., acquired Cloudscape, Inc.. 
+In 2001, IBM acquired the database assets of Informix Software, 
 including Cloudscape. 
-The database engine was re-branded to IBM Cloudscape and releases continued, 
+IBM re-branded the database engine as IBM Cloudscape and releases continued, 
 mainly focussing on embedded use with IBM's Java products and middleware. 
-In August 2004 IBM contributed the code to the Apache Software Foundation
+In August 2004, IBM contributed the code to the Apache Software Foundation
 as Derby, an Incubator project sponsored by the Apache DB project
 (<a href="derby_proposal.html">see the Incubator proposal</a>).
-In July 2005 Derby graduated from the Incubator into the Apache DB project.
+In July 2005, Derby graduated from the Incubator as an Apache DB sub-project.
-<em>Last updated: 14-February-2006</em>
+<em>Last updated: 09-September-2017</em>

Modified: db/derby/site/trunk/src/documentation/content/xdocs/derby_downloads.xml
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/derby_downloads.xml?rev=1807935&r1=1807934&r2=1807935&view=diff
--- db/derby/site/trunk/src/documentation/content/xdocs/derby_downloads.xml (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/derby_downloads.xml Sat Sep  9 23:45:38
@@ -26,22 +26,29 @@
-<title> Latest Official Releases </title>
+<title>For Java 8 and Higher</title>
    <li> <a href="releases/release-"></a> 
    (October 25, 2016 / SVN 1766613)
-   <li> <a href="releases/release-"></a> 
-   (October 11, 2015 / SVN 1704137)
-   </li>
-<title>Archived Official Releases</title>
+<title>For Java 6 and Higher</title>
+   <li> <a href="releases/release-"></a> 
+   (October 11, 2015 / SVN 1704137)
+   </li>
    <li> <a href="releases/release-"></a> 
    (August 26, 2014 / SVN 1616546)
+<title>For Java 1.4 and Higher</title>
    <li> <a href="releases/release-"></a> 
    (April 15, 2014 / SVN 1582446)
@@ -84,6 +91,12 @@
    <li> <a href="releases/release-"></a> 
    (April 24, 2008 / SVN 648739)
+<title>For Java 1.3 and Higher</title>
    <li> <a href="releases/release-"></a> 
    (Dec 12, 2006 / SVN 485682)

Modified: db/derby/site/trunk/src/documentation/content/xdocs/faq.xml
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/faq.xml?rev=1807935&r1=1807934&r2=1807935&view=diff
--- db/derby/site/trunk/src/documentation/content/xdocs/faq.xml (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/faq.xml Sat Sep  9 23:45:38 2017
@@ -93,10 +93,10 @@
             <a href="http://www.google.com/help/refinesearch.html">domain 
            For example, the search string below looks for all references
-           to "create table" in the 10.7 documentation set:
+           to "create table" in the 10.13 documentation set:
-"create table" site:db.apache.org/derby/docs/10.7
+"create table" site:db.apache.org/derby/docs/10.13
@@ -186,10 +186,10 @@
     <faq id="derby_eclipse">
-        How do you build Derby using Eclipse?
+        How do you build Derby using Eclipse or Netbeans?
-	<p>See the Eclipse instructions in the 
+	<p>See the Eclipse and Netbeans instructions on the 
         <a href="http://wiki.apache.org/db-derby/BuildingDerby">BuildingDerby</a>
         Wiki page.
@@ -256,7 +256,7 @@
     <faq id="pda">
-      Can you run Derby on PDAs?
+      Can you run Derby on small devices?
@@ -264,52 +264,18 @@
       J2ME/CDC/Foundation with JSR169 as the JDBC api. 
       For more information, see the 
 <a href="http://db.apache.org/derby/docs/10.7/ref/rrefjdbcjsr169.html">Reference
-      Guide</a>.
+      Guide</a>. Starting with 10.11, Derby added support for running on the small
Java 8 compact profile 2 platform.
-    <faq id="createdb_OS_X">
-      <question>
-        Why can't I create a new database or modify an existing database 
-	on Mac OS X?
-      </question>
-      <answer>
-        <p>
-	This appears to be a JVM issue with Derby on Mac OS X and 
-	 was logged as 
-	<a href="http://issues.apache.org/jira/browse/DERBY-1">DERBY-1</a>.
-        DERBY-1 is fixed in and higher. If you are using an earlier
-        version of Derby, upgrading to or higher will prevent the need
-        to use the workaround described below.
-        The underlying JVM issue is fixed in Mac OS X 10.4 (Tiger) with J2SE 1.4.2, 
-        but remains a problem on Mac OS X 10.3 with Java 1.4.2 Update 2 and
-        Mac OS X 10.4 with J2SE 5.0 Release 1. It has been fixed in more recent
-        releases of the J2SE 5.0 JVM.
-	The workaround is to set
-	<a href="http://issues.apache.org/jira/browse/DERBY-1?page=comments#action_53617">derby.storage.fileSyncTransactionLog=true</a>
-	in the derby.properties files to use file 
-	sync instead of write sync for log writes.
-	</p>
-      </answer>
-    </faq>
     <faq id="derby_javax">
       Can I use Derby on Java release X?
-        Derby runs on Java 1.4 and newer (Derby 10.2 and earlier also
-        runs with Java 1.3, should you need that).
-      </p>
-      <p>
-      Two problems with handling Decimal conversion on 
-      Java 5.0 and newer:
-      (<a href="http://issues.apache.org/jira/browse/DERBY-74">DERBY-74</a>
-      and
-      <a href="http://issues.apache.org/jira/browse/DERBY-83">DERBY-83</a>)
-      were fixed in Derby 10.1. Note: Java 5.0 is also known as 
-      <a href="http://java.sun.com/j2se/naming_versioning_5_0.html">
-      Java 1.5</a>.
+        See the <a href="derby_downloads.html">Derby Downloads</a> page
+        for the compatibility between Derby and Java versions.
@@ -320,7 +286,7 @@
-      Yes, Derby now supports such a configuration! For more information,
+      Of course! For more information,
       start <a href="http://wiki.apache.org/db-derby/InMemoryBackEndPrimer">
@@ -338,7 +304,7 @@
       <a href="integrate/SQuirreL_Derby.html">SQuirreL SQL</a>
       with Derby, and the
       <a href="http://wiki.apache.org/db-derby/UsesOfDerby">UsesOfDerby</a>
-      Wiki page list GUIs that work with Derby.
+      Wiki page list other GUIs that work with Derby.
@@ -351,7 +317,7 @@
       You can specify a
       database name using an absolute or relative path.
       Details are in the
-      <a href="http://db.apache.org/derby/docs/10.7/devguide/cdevdvlp34964.html">Developer's
+      <a href="http://db.apache.org/derby/docs/10.13/devguide/cdevdvlp34964.html">Developer's
       and helpful tips are on the
       <a href="http://wiki.apache.org/db-derby/DatabaseNamesRelativeAbsolute">Derby
@@ -411,9 +377,9 @@
           Derby does not support the LIMIT syntax. However, Derby 10.4
-          added the <a href="http://db.apache.org/derby/docs/10.7/ref/rreffuncrownumber.html">ROW_NUMBER
+          added the <a href="http://db.apache.org/derby/docs/10.13/ref/rreffuncrownumber.html">ROW_NUMBER
           and Derby 10.7 added the
-          <a href="http://db.apache.org/derby/docs/10.7/ref/rrefsqljoffsetfetch.html">OFFSET
and FETCH clauses</a>.
+          <a href="http://db.apache.org/derby/docs/10.13/ref/rrefsqljoffsetfetch.html">OFFSET
and FETCH clauses</a>.
       Derby also supports limiting the number of rows returned by a query through
       <a href="http://mail-archives.apache.org/mod_mbox/db-derby-dev/200411.mbox/%3c41A95632.3010301@debrunners.com%3e">JDBC</a>.
For example, to fetch the first 5 rows of a large table:
@@ -548,9 +514,9 @@
         Also, Derby supports generated "identity" columns; examples are in
-        <a href="http://db.apache.org/derby/docs/10.7/ref/rrefsqlj37836.html">Reference
+        <a href="http://db.apache.org/derby/docs/10.13/ref/rrefsqlj37836.html">Reference
-        <a href="http://db.apache.org/derby/docs/10.7/ref/rrefidentityvallocal.html#rrefidentityvallocal">IDENTITY_VAL_LOCAL</a>
+        <a href="http://db.apache.org/derby/docs/10.13/ref/rrefidentityvallocal.html#rrefidentityvallocal">IDENTITY_VAL_LOCAL</a>
         function returns the most recently assigned number.
@@ -565,15 +531,14 @@
       Yes, you can use derby for client-server applications.
-      Starting in 10.1 Derby includes the
-      <a href="http://db.apache.org/derby/docs/10.7/adminguide/cadminappsclient.html">Derby
Network Client jdbc driver</a>.
+      Starting in 10.1 Derby included the
+      <a href="http://db.apache.org/derby/docs/10.13/adminguide/cadminappsclient.html">Derby
Network Client jdbc driver</a>.
       The <a href="http://wiki.apache.org/db-derby/UsesOfDerby">UsesOfDerby</a>
       Wiki pages lists additional drivers, including
-      <a href="http://c-jdbc.objectweb.org/">C-JDBC</a>,
-      the
+      <a href="http://c-jdbc.objectweb.org/">C-JDBC</a>
+      and the
       <a href="http://www.ibm.com/developerworks/db2/downloads/jcc/">IBM
-      DB2 JDBC Universal Driver</a>, and
-      <a href="http://sequoia.continuent.org/HomePage">Sequoia</a>.
+      DB2 JDBC Universal Driver</a>.
@@ -586,7 +551,7 @@
       Yes, Apache Derby has a JDBC driver
       that works with the Derby Network Server.
       It is called the
-      <a href="http://db.apache.org/derby/docs/10.7/adminguide/cadminappsclient.html">Derby
Network Client</a>
+      <a href="http://db.apache.org/derby/docs/10.13/adminguide/cadminappsclient.html">Derby
Network Client</a>
       and it became available starting with Derby 10.1.
@@ -617,7 +582,7 @@
       XA support using Network Server allows you to do this and the
       Derby Network Client, new in 10.1, supports this functionality.
       An example of establishing an XA connection is in the 
-      <a href="http://db.apache.org/derby/docs/10.7/adminguide/cadminapps811478.html">Admin
and Server Guide</a>.
+      <a href="http://db.apache.org/derby/docs/10.13/adminguide/cadminapps811478.html">Admin
and Server Guide</a>.
@@ -634,18 +599,18 @@
          Use PreparedStatement with dynamic markers('?') instead of Statement. 
          This will be faster since the statement does not need to be 
          recompiled every time. See the
-<a href="http://db.apache.org/derby/docs/10.7/tuning/ctunperf18705.html">Use prepared
statements with substitution parameters</a> and
-<a href="http://db.apache.org/derby/docs/10.7/tuning/ctundepth29804.html#ctundepth29804">Avoid
compiling SQL statements</a> sections of the Tuning Derby guide.
+<a href="http://db.apache.org/derby/docs/10.13/tuning/ctunperf18705.html">Use prepared
statements with substitution parameters</a> and
+<a href="http://db.apache.org/derby/docs/10.13/tuning/ctundepth29804.html#ctundepth29804">Avoid
compiling SQL statements</a> sections of the Tuning Derby guide.
         Avoid inserts in autocommit mode if possible. 
-        Inserts can be painfully slow in autocommit mode. 
-        The reason is that each commit involves a flush of the 
+        Autocommitted inserts
+        flush of the 
         log to the disk for each insert statement. 
-        The commit will not return until a physical disk write has been 
+        The commit does not return until a physical disk write has been 
-        So to speed things up, run in autocommit false mode and 
-        execute a number of inserts in one transaction and then explicitly 
+        So to speed things up, run in autocommit false mode,
+        execute a number of inserts in one transaction, and then explicitly 
         issue a commit.
@@ -658,7 +623,7 @@
       The <em>Reference Guide</em> includes an 
-      <a href="http://db.apache.org/derby/docs/10.7/ref/rrefclob.html">example
+      <a href="http://db.apache.org/derby/docs/10.13/ref/rrefclob.html">example
       that shows how to insert a CLOB</a>.
       <a href="http://mail-archives.apache.org/mod_mbox/db-derby-user/200509.mbox/%3c1126857139.2375.75.camel@pc977.sb.statsbiblioteket.dk%3e">this

Modified: db/derby/site/trunk/src/documentation/content/xdocs/index.xml
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/index.xml?rev=1807935&r1=1807934&r2=1807935&view=diff
--- db/derby/site/trunk/src/documentation/content/xdocs/index.xml (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/index.xml Sat Sep  9 23:45:38 2017
@@ -33,7 +33,7 @@ Some key advantages include:
-  <li> Derby has a small footprint -- about 2.6 megabytes for the base engine
+  <li> Derby has a small footprint -- about 3.5 megabytes for the base engine
        and embedded JDBC driver.</li>
   <li> Derby is based on the Java, JDBC, and
        <a href="http://wiki.apache.org/db-derby/SQLvsDerbyFeatures">SQL</a>

Modified: db/derby/site/trunk/src/documentation/content/xdocs/license.xml
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/license.xml?rev=1807935&r1=1807934&r2=1807935&view=diff
--- db/derby/site/trunk/src/documentation/content/xdocs/license.xml (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/license.xml Sat Sep  9 23:45:38 2017
@@ -33,8 +33,6 @@ Also see:
- <li> <a href="http://www.apache.org/foundation/licence-FAQ">Apache 
-       Licensing FAQ</a></li>
  <li> <a href="http://www.apache.org/dev/apply-license.html">Applying the
        Apache License, Version 2.0</a></li>
  <li> Cliff Schmidt's ApacheCon presentation titled
@@ -52,7 +50,7 @@ Also see:
-<em>This page last updated: 1-November-2005</em>
+<em>This page last updated: 09-September-2017</em>

View raw message