Relicensed and downloadable (Re: Protocol 3, Execute, maxrows to return, impact?)

From: "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
To: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Relicensed and downloadable (Re: Protocol 3, Execute, maxrows to return, impact?)
Date: 2008-07-29 10:55:04
Message-ID: 20080729105504.GA18800@cuci.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Limited offer, get it while it's hot:

http://admin.cuci.nl/pgsql.pike.driver.tar.gz.bin

I relicensed it under BSD now, put up proper copyright notices, and
included the accelleratorclass for amusement (the module works without
the accellerator class, but it's about 10 times slower than libpq then).

For anyone trying to understand Pike, the important points probably are
that:
- ({ 1, 2, 3, 4 }) is an array.
- m = (["key1":13, "key2":14, "key3":15]) is a mapping, i.e. m->key1
or m["key1"] both evaluate to 13.

The rest is rather similar to C++/Java.

See http://pike.roxen.com/ for more documentation and references,
try git://git.cuci.nl/pike as the source repository,
http://pike.ida.liu.se/docs/ for documentation and tutorials.

The fetch_row() function actually returns an array for each row, where
the individual columns are already parsed and converted into the native
Pike formats for handling.
--
Sincerely,
Stephen R. van den Berg.

"People who think they know everything are annoying to those of us who do."

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2008-07-29 10:56:17 Re: [WIP] patch - Collation at database level
Previous Message Asko Oja 2008-07-29 10:52:20 Re: [PATCH] "\ef <function>" in psql