Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 25741 invoked from network); 9 Jul 2009 14:39:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Jul 2009 14:39:55 -0000 Received: (qmail 23978 invoked by uid 500); 9 Jul 2009 14:40:04 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 23903 invoked by uid 500); 9 Jul 2009 14:40:04 -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 23867 invoked by uid 99); 9 Jul 2009 14:40:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jul 2009 14:40:04 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dmclean62@gmail.com designates 209.85.132.248 as permitted sender) Received: from [209.85.132.248] (HELO an-out-0708.google.com) (209.85.132.248) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jul 2009 14:39:54 +0000 Received: by an-out-0708.google.com with SMTP id d40so76875and.40 for ; Thu, 09 Jul 2009 07:39:33 -0700 (PDT) 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 :content-transfer-encoding; bh=r+VgehGMvo1YmWvXwwpJGnBugbpLJ6vg6HcotmwHd0U=; b=oW5nJAFywNhyfmgdDf+Mdsw3Mi8b3O0P7fZkx9uThuFROS7niY9f5Asp0d6dfMcQnb PBMlcsPBMKiS/Rf/Zer06jFm8aEXlN5a74OP1IPwXUpA+UVvZkeCOchLKa5DcF6elvdl kt3ZRbNgpKXMVSDUQc0Wm0XO5cMbAuS4/Ypr4= 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:content-transfer-encoding; b=WZc9HfS26d0cRGVt3LW9RY2entl/h1RTU4eX5TFgSJtZdUkfEuRdwMwjgEpjpWKVXo T8UEuP9bDf+IO92AbbTvkvV/UeJR0LfRbKKJJ/YMyLRLvI9nr2afoEFjAExFEqID2R0Z +oWDAf3WnUFNgAqvaG339sFGV+AbgbGn/2uOY= MIME-Version: 1.0 Received: by 10.100.215.12 with SMTP id n12mr1176136ang.133.1247150373830; Thu, 09 Jul 2009 07:39:33 -0700 (PDT) In-Reply-To: <4d2670740907090732i13a23a2amd6b5574a57d9bcb1@mail.gmail.com> References: <4A55EA88.1010506@yahoo.it> <5627810d0907090630p768223f9sf08d911a92546a70@mail.gmail.com> <4d2670740907090732i13a23a2amd6b5574a57d9bcb1@mail.gmail.com> Date: Thu, 9 Jul 2009 10:39:33 -0400 Message-ID: <5627810d0907090739l6a7f6e11qa50e863f2a495506@mail.gmail.com> Subject: Re: How would you implement a record-level versioning system with Derby and Java? From: Donald McLean To: Derby Discussion Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org I like that idea. You could even create different tables for different epoc= hs. On Thu, Jul 9, 2009 at 10:32 AM, Peter Ondru=C5=A1ka wrote: > Actually I would store the history values outside the main table for > performance and storage overhead reasons (history table may have > additional columns, e.g. When-who-etc for auditing information). Peter ------------------------------------------------------------- Family photographs are a critical legacy for ourselves and our descendants. Protect that legacy with a digital backup and recovery plan.