From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.3 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by yquem.inria.fr (Postfix) with ESMTP id 8882DBC69 for ; Sat, 12 May 2007 22:31:53 +0200 (CEST) Received: from mail.enyo.de (mail.enyo.de [212.9.189.167]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id l4CKVqPv019242 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Sat, 12 May 2007 22:31:53 +0200 Received: from deneb.vpn.enyo.de ([212.9.189.177] helo=deneb.enyo.de) by mail.enyo.de with esmtp id 1HmyFq-0000IC-Mp; Sat, 12 May 2007 22:31:50 +0200 Received: from fw by deneb.enyo.de with local (Exim 4.67) (envelope-from ) id 1HmyFl-0004X1-Da; Sat, 12 May 2007 22:31:45 +0200 From: Florian Weimer To: Oliver Bandel Cc: caml-list@inria.fr Subject: Re: [Caml-list] [ 1/2 OT ;-) ] This sounds very functional to me... References: <20070512102633.GA520@first.in-berlin.de> Date: Sat, 12 May 2007 22:31:45 +0200 In-Reply-To: <20070512102633.GA520@first.in-berlin.de> (Oliver Bandel's message of "Sat, 12 May 2007 12:26:33 +0200") Message-ID: <87646xg4we.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Miltered: at concorde with ID 46462438.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; bandel:01 overwrite:01 oliver:01 caml-list:01 data:02 data:02 functional:02 functional:02 florian:03 locks:03 table:93 space:07 quite:07 row:07 background:91 * Oliver Bandel: > "PostgreSQL creates a new version of the row and also retains the > old or expired version. Database systems that use row-level > locking do not retain old versions of the data, hence the need > for locks to maintain data consistency." > > this sounds very functional to me, > like non-destructive updates/functional datastructures... > > ... does FP ideas become more and more popular? Quite a few database people (often those with a background in accounting) tell you that you should never overwrite any data. Early versions of PostgreSQL followed that closely, so you could not delete any data and free up the space (but you were able to time-travel to older table versions).