From: Florian Weimer <fw@deneb.enyo.de>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ 1/2 OT ;-) ] This sounds very functional to me...
Date: Sat, 12 May 2007 22:31:45 +0200 [thread overview]
Message-ID: <87646xg4we.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20070512102633.GA520@first.in-berlin.de> (Oliver Bandel's message of "Sat, 12 May 2007 12:26:33 +0200")
* 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).
prev parent reply other threads:[~2007-05-12 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 10:26 Oliver Bandel
2007-05-12 10:27 ` [Caml-list] " Jon Harrop
2007-05-14 2:15 ` Robert Fischer
2007-05-14 10:01 ` skaller
2007-05-12 20:31 ` Florian Weimer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87646xg4we.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox