Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 40458 invoked from network); 30 Nov 2009 16:27:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Nov 2009 16:27:00 -0000 Received: (qmail 49428 invoked by uid 500); 30 Nov 2009 16:27:00 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 49339 invoked by uid 500); 30 Nov 2009 16:26:59 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 49331 invoked by uid 99); 30 Nov 2009 16:26:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Nov 2009 16:26:59 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dmclean62@gmail.com designates 209.85.211.195 as permitted sender) Received: from [209.85.211.195] (HELO mail-yw0-f195.google.com) (209.85.211.195) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Nov 2009 16:26:56 +0000 Received: by ywh33 with SMTP id 33so3415334ywh.23 for ; Mon, 30 Nov 2009 08:26:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=G681v6Hs6RIhrg6v6eX5HOBT4b8fDFeqZLsWDYVm56s=; b=ragGmOzw7HapB9xOR6s0jAj9l3VIOASGB3MtimQgiIZ7KSc+G+VRRL5YpBFfLupl2z 8HLYQ4zXhlXRWOC/kDuSyvukADAq2RKf3tjxlod1qn+kDKRsdfoy4Pb520zNhiInQXD6 0/A/fJYcfgOF9u5QTFeTkFiDEIQ1KfWr3NEB0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=XPazRmf0oQUQUWq7QQ/ntvKgruKQOqPtNR4NmHIoghCGnpVGJCZKfJ3vtz2Tjiu+mO GQsTU8VEvAU+KDpDcwG0cSCnZ3pD8r+nJMrSUl07PYUggyG/iwtmIjRgjtV/xcfSG6sM tSRykijQBgnxZk1KLmZ4fhg+wqcwFP39A7WSU= MIME-Version: 1.0 Received: by 10.101.113.11 with SMTP id q11mr1600234anm.178.1259598395849; Mon, 30 Nov 2009 08:26:35 -0800 (PST) In-Reply-To: <200911302350089810482@qq.com> References: <200911302350089810482@qq.com> Date: Mon, 30 Nov 2009 11:26:35 -0500 Message-ID: <5627810d0911300826y444f7f9cj8df18adf864cefe1@mail.gmail.com> Subject: Re: Derby--Embedded From: Donald McLean To: Derby Discussion Content-Type: text/plain; charset=ISO-8859-1 Oracle and other databases (including Derby server mode) - the DB runs as a separate process and the application talks to it over a network connection. Embedded databases such as Derby the database runs inside your application, the database is on a local disk and the application objects talk directly to the DBMS objects via method calls. Actually doing the embedding basically requires two things: 1. including derby.jar in your classpath 2. connecting to the database using a URL that specifies a local file Otherwise - what Rick said - the Derby documentation is pretty straightforward and useful. Donald On Mon, Nov 30, 2009 at 10:50 AM, 120113698 <120113698@qq.com> wrote: > How can I embed the Derby-Database to a Desktop Java Application? > and what is the deffirence between using Oracle Database in Deaktop Java > Apps and using derby in desktop java apps? -- Family photographs are a critical legacy for ourselves and our descendants. Protect that legacy with a digital backup and recovery plan. Join the photo preservation advocacy Facebook group: http://www.facebook.com/home.php?ref=logo#/group.php?gid=148274709288