Relicensed and downloadable (Re: Protocol 3, Execute, maxrows to return, impact?) - Mailing list pgsql-hackers

From Stephen R. van den Berg
Subject Relicensed and downloadable (Re: Protocol 3, Execute, maxrows to return, impact?)
Date
Msg-id 20080729105504.GA18800@cuci.nl
Whole thread Raw
In response to Re: Protocol 3, Execute, maxrows to return, impact?  ("Stephen R. van den Berg" <srb@cuci.nl>)
Responses Re: Relicensed and downloadable (Re: Protocol 3, Execute, maxrows to return, impact?)  ("Stephen R. van den Berg" <srb@cuci.nl>)
List 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."


pgsql-hackers by date:

Previous
From: "Asko Oja"
Date:
Subject: Re: [PATCH] "\ef " in psql
Next
From: "Asko Oja"
Date:
Subject: Re: [PATCH] "\ef " in psql