[ 1/2 OT ;-) ] This sounds very functional to me...

[ 1/2 OT ;-) ] This sounds very functional to me...

[Oliver Bandel]

Hello,


  "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?

The quote is from:

  http://www.onlamp.com/pub/a/onlamp/2001/05/25/postgresql_mvcc.html

OK, it's not absolutely new, but it's > y2k. ;-)

I also heard of gcc that newer versions use FP-like ideas....


Ciao,
   Oliver

Re: [Caml-list] [ 1/2 OT ;-) ] This sounds very functional to me...

[Jon Harrop]

On Saturday 12 May 2007 11:26, Oliver Bandel wrote:
> ... does FP ideas become more and more popular?

Yes. The LINQ project brings functional programming to databases. Both Java 
and C# are adopting functional features (like closures).

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
The F#.NET Journal
http://www.ffconsultancy.com/products/fsharp_journal/?e

Re: [Caml-list] [ 1/2 OT ;-) ] This sounds very functional to me...

[Robert Fischer]

The functional revolution is underway, people just don't realize it yet. 
My favorite example is Java's revolutionary "Spring" framework, which uses
"inversion of control" -- basically just a weak, limited version of
function passing.  Sooner or later business will start to realize they
need to move beyond Java/C#: it's just going to take some nudging along.

~~ Robert.

On Sat, May 12, 2007 5:27 am, Jon Harrop wrote:
> On Saturday 12 May 2007 11:26, Oliver Bandel wrote:
>> ... does FP ideas become more and more popular?
>
> Yes. The LINQ project brings functional programming to databases. Both
> Java
> and C# are adopting functional features (like closures).
>
> --
> Dr Jon D Harrop, Flying Frog Consultancy Ltd.
> The F#.NET Journal
> http://www.ffconsultancy.com/products/fsharp_journal/?e
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>


~~ Robert Fischer.
Fischer Venture Management Corporation

Re: [Caml-list] [ 1/2 OT ;-) ] This sounds very functional to me...

[skaller]

On Sun, 2007-05-13 at 21:15 -0500, Robert Fischer wrote:
> The functional revolution is underway, people just don't realize it yet. 

Isn't it just so typically there begins to be support for it,
at a time theorists are moving to understand stateful systems.

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net

Re: [Caml-list] [ 1/2 OT ;-) ] This sounds very functional to me...

[Florian Weimer]

* 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).