From general-return-536-apmail-db-general-archive=db.apache.org@db.apache.org Wed Dec 19 18:21:16 2012 Return-Path: X-Original-To: apmail-db-general-archive@www.apache.org Delivered-To: apmail-db-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A3DA3DC92 for ; Wed, 19 Dec 2012 18:21:16 +0000 (UTC) Received: (qmail 49139 invoked by uid 500); 19 Dec 2012 18:21:16 -0000 Delivered-To: apmail-db-general-archive@db.apache.org Received: (qmail 49094 invoked by uid 500); 19 Dec 2012 18:21:16 -0000 Mailing-List: contact general-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: general@db.apache.org List-Id: Delivered-To: mailing list general@db.apache.org Received: (qmail 49087 invoked by uid 99); 19 Dec 2012 18:21:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2012 18:21:16 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2012 18:21:08 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 8414B23889E0 for ; Wed, 19 Dec 2012 18:20:46 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r843115 [5/44] - in /websites/production/db/content/derby: ./ binaries/ blogs/ blogs/images/ dev/ docs/ images/ integrate/ integrate/plugin_help/ integrate/plugin_help/images/ logo/ manuals/ papers/ papers/DerbyTut/ releases/ skin/ skin/css... Date: Wed, 19 Dec 2012 18:20:28 -0000 To: general@db.apache.org From: rhillegas@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20121219182046.8414B23889E0@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Added: websites/production/db/content/derby/derby_mail.html ============================================================================== --- websites/production/db/content/derby/derby_mail.html (added) +++ websites/production/db/content/derby/derby_mail.html Wed Dec 19 18:20:21 2012 @@ -0,0 +1,481 @@ + + + + + + + +Apache Derby: Mailing Lists + + + + + + + + + +
+ +
+apache > db +
+ +
+ + + + +
+Apache DB Project +
+ + + + +
+
+
+
+ +
+ + +
+ +
+ +   +
+ + + + + +
+
Font size: +   +   +   +
+

Apache Derby: Mailing Lists

+ + +

+Information about participating in Apache mail lists include: +

+ + + + + +

+Derby lists are managed by ezmlm. +To obtain information about a mail list, +send email to list-info@apache.org. +For example, to get a summary of derby-user mail list features, +send email to +derby-user-info@db.apache.org. +The response will tell you what other list commands are supported; +for example, it will tell you that you can subscribe to the derby-user digest by sending email to +derby-user-digest-subscribe@db.apache.org. +

+ + +

+Anyone can subscribe to the Derby lists; +however, the first post is moderated to keep spam out. +Be patient. +Your first post will appear as soon as a moderator allows it. +And only your first post is moderated; +subsequent posts will appear automatically. +

+ + +

+Sometimes a post bounces with a "spam score exceeded threshold" message. +It helps to turn off html formatting of messages (eliminating html also makes +posts consistently readable in the Apache mod_mbox mail archives). +Also, when you subscribe to a list, +it helps to enter text (any text) into the Subject and the Body of the message. +If problems still occur, you can reach the list moderators at +list-owner@apache.org; for example, derby-user-owner@db.apache.org. +

+ + +

+If you're curious about mail list traffic see +The Apache Software +Foundation Mailing Lists (you'll find the Derby lists in the +db.apache.org +section). +

+ + +

+The table below summarizes the Derby mail lists and shows some (but not all) +of the places where they are archived. +To subscribe or unsubscribe send an email to the address noted. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Mail listLinks
Derby UsersPurpose:For discussions about how to use Derby.
Post:derby-user@db.apache.org
List subscribe: derby-user-subscribe@db.apache.org
List unsubscribe:derby-user-unsubscribe@db.apache.org
Digest subscribe: derby-user-digest-subscribe@db.apache.org
Digest unsubscribe:derby-user-digest-unsubscribe@db.apache.org
Archives (mod_mbox): + http://mail-archives.apache.org/mod_mbox/db-derby-user +
Archives (gmane): +http://news.gmane.org/gmane.comp.apache.db.derby.user +
Archives (nabble): +http://www.nabble.com/Apache-Derby-Users-f93.html +
Archives (MarkMail): +http://db.markmail.org/search/list:org.apache.db.derby-user +
Derby DevelopersPurpose:For discussions about development tasks, such as + bug fixes, proposed code changes, etc.
Post:derby-dev@db.apache.org
List subscribe: derby-dev-subscribe@db.apache.org
List unsubscribe:derby-dev-unsubscribe@db.apache.org
Digest subscribe: derby-dev-digest-subscribe@db.apache.org
Digest unsubscribe:derby-dev-digest-unsubscribe@db.apache.org
Archives (mod_mbox): + http://mail-archives.apache.org/mod_mbox/db-derby-dev +
Archives (gmane): +http://news.gmane.org/gmane.comp.apache.db.derby.devel +
Archives (nabble): +http://www.nabble.com/Apache-Derby-Developers-f91.html +
Archives (MarkMail): +http://db.markmail.org/search/list:org.apache.db.derby-dev +
Derby CommitsPurpose:For Derby commit records, which automatically get posted by Subversion.
List subscribe: derby-commits-subscribe@db.apache.org
List unsubscribe:derby-commits-unsubscribe@db.apache.org
Archives (mod_mbox): + http://mail-archives.apache.org/mod_mbox/db-derby-commits +
+ + +

+ +Last updated: December 1, 2007 + +

+ + +
+ +
 
+
+ + + Added: websites/production/db/content/derby/derby_proposal.html ============================================================================== --- websites/production/db/content/derby/derby_proposal.html (added) +++ websites/production/db/content/derby/derby_proposal.html Wed Dec 19 18:20:21 2012 @@ -0,0 +1,666 @@ + + + + + + + +Proposal for Derby: an Apache Database Sub-Project + + + + + + + + + +
+ +
+apache > db +
+ +
+ + + + +
+Apache DB Project +
+ + + + +
+
+
+
+ +
+ + +
+ +
+ +   +
+ + + + + +
+
Font size: +   +   +   +
+

Proposal for Derby: an Apache Database Sub-Project

+ + + +

+Submitted July 20, 2004 +

+ + + +

Section 0 : Rationale

+
+

Databases are a core component of nearly all applications. But +traditional database servers are expensive to install, configure +and maintain, raising the total cost of ownership for building +and deploying applications. The complexity of traditional +database servers - whether commercial or open source - hinders +the pace of innovation in application development.

+

What's needed is a much easier to use database - written in +Java with all of the advantages of Java's portability - that +doesn't sacrifice the benefits and features of a full-function +relational database. The database needs to install when the +application is installed, run when the application runs, stop +when the application stops, and upgrade when the application +upgrades. Unless the application developer wishes, the +application user/administrator should not need to worry about the +database underlying the application.

+

Besides providing all of the functionality of modern +relational databases - complete SQL syntax, transaction commit +and rollback, high concurrency, triggers, online backup, etc. - +the database must adhere to appropriate standards for relational +databases. Standards are key, as developers should not have to +sacrifice their favorite development tools to use the database, +nor should they incur undesirable expense if they later port to a +different database.

+

Our goal is to produce a community of developers - with +backgrounds in Database Engineering, SQL-92 and SQL-99 standards, +data-centric applications, and XML-related technologies such as +XML-Query - whose mission is to provide a standards-based, +full-featured relational database with the aforementioned +features. The produced software will be Apache Software +Foundation (ASF) licensed.

+

The starting point for this project will be a contribution by +IBM to the ASF of "Derby", a pure-Java, full-featured relational +database based on a snapshot of the current IBM Cloudscape +product. Derby can be used in several configurations:

+
    + +
  • As an embedded database engine that runs within the same JVM +as the application. So the database starts when the application +starts, stops when the application stops, and requires no skills +or effort to administer by the user/administrator of the +application.
  • + + +
  • As a networked database server that runs in a separate JVM +and accepts network connections.
  • + + +
  • As a combination of these two configurations that provides +simplicity for the application developer/administrator plus +remote access to the database when desired.
  • + +
+
+ + + +

Section 0.1 : Criteria

+
+

We feel that this project has an excellent chance for success +as measured by the following aspects:

+
    + +
  • +Meritocracy: The project will be meritocratic - the + usual Apache meritocracy rules would apply.
  • + + +
  • +Community: The user community for this project will be + large. IBM's internal experience was enthusiastic and widespread + adoption of Cloudscape by 70+ projects due to its functionality + and ease-of-use characteristics. We believe these same advantages + will benefit many users and developers and will result in a large + community.
  • + + +
  • +Core Developers: IBM is dedicating developers to the + Derby project and is actively seeking additional developers from + the community to join the project.
  • + + +
  • +Alignment: As a full-featured SQL database with a JDBC + API, the Derby package aligns well with other Apache projects: + +
      + +
    • Apache Geronimo - Derby fulfills the JDBC requirement for + J2EE 1.3 and 1.4 and can be used successfully with the Geronimo + project.
    • + + +
    • Apache Tomcat - Derby can be embedded in Tomcat for a + self-contained web-application with database functionality. (Has + already been demonstrated.)
    • + + +
    • Apache DB - Cloudscape is currently listed as a supported + back-end for Torque. Derby could be a supported back-end for + ORB
    • + + +
    • Other possible integration points for Derby include Apache + Cocoon, multiple projects under Apache Jakarta, and integration + with Apache Xerces.
    • + +
    + +
  • + +
+
+ + + +

Section 1 : Scope of the Project

+
+

There are multiple goals for this Apache project:

+
    + +
  • Promote a healthy open source community.
  • + + +
  • Support the breadth of platforms that run Java with a + relational database that adheres rigorously to open + standards.
  • + + +
  • Promote a standards-based, database-agnostic approach to + application development.
  • + + +
  • Encourage innovation in application development and + deployment by offering: + +
      + +
    • an easy to use, full-featured relational database for use + during application development
    • + + +
    • an easy to deploy database for use in new applications
    • + + +
    • an easy to manage database for production users with modest + scalability requirements
    • + + +
    • a standards-based relational database such that users could + upgrade later to larger, more complex database server offerings + if scalability requirements demand
    • + + +
    • an ongoing commitment to maintaining a migration path to + other open standards databases
    • + +
    + +
  • + +
+
+ + + +

Section 2 : Initial Source

+
+

The initial code base from which to create this project is +from the commercial product called IBM Cloudscape. The history of this +product is that it was developed at Cloudscape Inc. starting in +1996. The Cloudscape product was purchased along with the +Cloudscape company by Informix Software in 1999. In 2001, IBM +purchased the database assets of Informix Software, including the +Cloudscape product.

+

IBM plans to contribute the Derby code base, test cases, build +files, and documentation to the ASF under the terms specified in +the ASF Corporate Contributor License. Once at Apache, the +project will be licensed under the ASF license.

+

Derby has the following features and benefits:

+
    + +
  • + +Zero administration: Derby + can be deployed in unsupervised environments, and does not + require database administration or resource management. This + eliminates the need for a database administrator at each client + installation site.
  • + + +
  • +Multiple platform compatibility: Derby + fully supports Sun Microsystems Java technology standards and + runs on any standard JVM V1.3, or later. It supports J2SE and + J2EE.
  • + + +
  • +Transactions and concurrency: Derby is highly + concurrent, and supports row-level locking and read-committed, + read-uncommitted, repeatable-read isolation levels, and + serializable isolation levels.
  • + + +
  • +Typical relational database features + + +
      + +
    • Fast query compilation
    • + + +
    • Bulk load
    • + + +
    • Multiple user support
    • + + +
    • Online backup
    • + + +
    • Crash recovery
    • + + +
    • Built-in performance diagnostics: Query statistics, locks, and + space usage
    • + +
    + +
  • + + +
  • +Advanced security features + + +
      + +
    • Signed JAR files
    • + + +
    • Optional LDAP and application-defined authentication
    • + + +
    • + Configurable disk encryption, supporting both diverse encryption + algorithms and encryption providers other than the default Java + Cryptography Extension (JCE) provider
    • + +
    + +
  • + + +
  • +Internationalization and localization support: Derby + supports Unicode and allows for localized error messages.
  • + + +
  • +SQL features + + +
      + +
    • SQL-92E compliance and supports key features in the SQL-99 + standards
    • + + +
    • Cost-based optimizer that supports hash joins, sort avoidance, + and row- or table-level locking based on percent of data + selected
    • + + +
    • Triggers
    • + + +
    • Foreign key and check constraints
    • + + +
    • Multicolumn B-Tree indexes
    • + + +
    • Multithreaded connections
    • + + +
    • Hold cursors
    • + + +
    • Temporary tables
    • + + +
    • BLOB/CLOB data types
    • + + +
    • Support for complex SQL transactions
    • + +
    + +
  • + + +
  • +Java features + + +
      + +
    • JDBC driver
    • + + +
    • Java procedures and functions
    • + + +
    • Storage of JAR files in the database, including signed JARs
    • + +
    + +
  • + +
+
+ + + +

Section 3 : ASF Resources to be Created

+
+ +

Section 3.1 : Mailing Lists

+ + +

Section 3.2 : CVS Repositories

+
    + +
  • incubator-derby
  • + +
+ +

Section 3.3 : Bugzilla or possibly Jira

+
    + +
  • TBD
  • + +
+
+ + + +

Section 4 : Initial Set of Committers

+
+

All committers will sign and submit a Contributors License + Agreement. To start the project in the incubator, the initial + committers from IBM will include:

+ +
+ + +

Section 5 : Apache Sponsoring Individuals

+
+
    + +
  • Apache DB project
  • + +
+
+ + +

Section 6 : Incubation Exit Criteria

+
+

We feel this project should exit the incubator to join the + Apache DB project should the following goals be met.

+

Technical Goals:

+
    + +
  • One or more Releases of the package during the incubation + phase
  • + +
+

Non-Technical Goals:

+
    + +
  • List presence and monitoring in wider Apache communities
  • + + +
  • Website cross reference to existing Apache literature with + respect to rules and regulations
  • + + +
  • Initial integration plan and cooperation with Apache DB and + Apache Jakarta projects
  • + + +
  • Additional contributors on the project
  • + +
+
+ + +
+ +
 
+
+ + + Added: websites/production/db/content/derby/derby_tests.html ============================================================================== --- websites/production/db/content/derby/derby_tests.html (added) +++ websites/production/db/content/derby/derby_tests.html Wed Dec 19 18:20:21 2012 @@ -0,0 +1,220 @@ + + + + + + + +Apache Derby: Tests + + + + + + + + + +
+ +
+apache > db +
+ +
+ + + + +
+Apache DB Project +
+ + + + +
+
+
+
+ +
+ + +
+ +
+ +   +
+ + + + + +
+
Font size: +   +   +   +
+

Apache Derby: Tests

+ + + +

+This page lists test results resources. +If you have questions about the results, or would like your results to be added to this page, send email to +derby-dev@db.apache.org. +

+ + + + + +

+ +Last updated: Jan 26, 2006 + +

+ + +
+ +
 
+
+ + + Added: websites/production/db/content/derby/dev/derby_source.html ============================================================================== --- websites/production/db/content/derby/dev/derby_source.html (added) +++ websites/production/db/content/derby/dev/derby_source.html Wed Dec 19 18:20:21 2012 @@ -0,0 +1,443 @@ + + + + + + + +Apache Derby: Source Code + + + + + + + + + +
+ +
+apache > db +
+ +
+ + + + +
+Apache DB Project +
+ + + + +
+
+
+
+ +
+ + +
+ +
+ +   +
+ + + + + +
+
Font size: +   +   +   +
+

Apache Derby: Source Code

+ + + + +

Intended Audience

+
+

+This page provides information for developers on how to check out +and build the Derby source code. +The official Derby releases are available on the +Downloads page. +

+
+ + + +

Derby source code

+
+

+Derby source is stored in the Subversion (SVN) repository at Apache. +For Derby web site source, see the +Apache Derby Web Site page. +The rest of this section describes where to get the Derby source code. +

+

+First, download and install Subversion from +http://subversion.tigris.org/ + +

+ +

Branches

+

+Currently Derby has the following branches: +

+
    + +
  • 10.9
  • + +
  • 10.8
  • + +
  • 10.7
  • + +
  • 10.6
  • + +
  • 10.5
  • + +
  • 10.4
  • + +
  • 10.3
  • + +
  • 10.2
  • + +
  • 10.1
  • + +
  • 10.0
  • + +
+

+Use the command shown below to check out the source code for a branch: +

+
svn co https://svn.apache.org/repos/asf/db/derby/code/branches/branch/
+
+

+Where branch is the number of the branch. +For example, the following command checks out the source code for +the 10.9 branch: +

+
svn co https://svn.apache.org/repos/asf/db/derby/code/branches/10.9/
+
+ +

Development trunk

+

+Use the command shown below to check out the development trunk: +

+
svn checkout https://svn.apache.org/repos/asf/db/derby/code/trunk/
+

+Production use of Derby should use official Derby releases or snapshot +builds off the branches (or self built jars off the branches with bug +fixes). +

+

+The development trunk +(http://svn.apache.org/repos/asf/db/derby/code/trunk) is +a development code line, which supports: +

+
    + +
  • Development of new features.
  • + +
  • Early access to new features for testing.
  • + +
+

+The development trunk is not +suitable for production use because: +

+
    + +
  • It contains new features that have only undergone limited testing + and that may corrupt data and/or return incorrect results. +
  • + + +
  • It may create on-disk database formats that are not upgradable to future + releases of Derby. Databases created by official Derby releases will be + upgradable to future versions. +
  • + +
+
+
Warning
+
+The alpha version tag explicitly disables upgrade in Derby. +
+
+
+ + + +

Software required to build Derby

+
+

+Derby is designed to work in JSR 169, JDBC 3.0, +and JDBC 4.1 environments. In addition, optional run-time +code may take advantage of features introduced by Java 5. +

+

+The software required to build the Derby mainline is summarized in the table below. +However, doublecheck the +BUILDING.html +instructions for installation locations before downloading the software. +(Note: if your browser shows HTML source for this page instead of +displaying it, +save the file locally with File -> Save Page As, +then open the file you saved.) +If +you need to build an earlier version of Derby, please consult the +build instructions in the appropriate code branch. For 10.4 and earlier branches, +those instructions live in a file called BUILDING.txt rather than BUILDING.html. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
SoftwareWhere to obtain it
Apache Ant 1.7.x + http://ant.apache.org/bindownload.cgi +
Java Development Kit (JDK) release 5 Any Java 5 JDK, Java's reference implementation is at + http://java.sun.com/j2se/ +
+
+ + + +

How to build Derby

+
+

+Instructions for building Derby are in a file named +BUILDING.html +at the root of the source code tree. +

+
+ + + +

How to test Derby

+
+

+Instructions for testing Derby are in the source code tree in +java/testing/README.htm. +

+

+The previous link points to java/testing/README.htm in the +development trunk. +If you want to access the instructions in a specific branch, +access the file directly by checking out the +branch +or the development trunk. +

+

+Also, see the tests page for test results +resources. +

+
+ + + +

How to submit a patch

+
+

+See the +Contribute Code +or Documentation section in the +Get Involved! page. +

+
+ + +

+ +Last updated: May 24, 2012 + +

+ + +
+ +
 
+
+ + +