Horton

Re: why does plperl cache functions using just a bool for is_trigger

David Wheeler <david@kineticode.com>

View thread
From: "David E. Wheeler" <david@kineticode.com>
To: Alex Hunsaker <badalex@gmail.com>
Cc: Jan Urbański <wulczer@wulczer.org>, Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, Postgres - Hackers <pgsql-hackers@postgresql.org>
Date: 2010-11-03T21:15:21Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove unnecessary use of trigger flag to hash plperl functions

On Nov 3, 2010, at 2:06 PM, Alex Hunsaker wrote:

>> try:
>>    plpy.execute("insert into foo values(1)")
>> except plpy.UniqueViolation, e:
>>    plpy.notice("Ooops, you got yourself a SQLSTATE %d", e.sqlstate)
> 
> Ouuu <googly eyes>.
> 
> [ now that eval { }, thanks to Tim Bunce, works with plperl it should
> be possible to do something similar there as well.  Just noting the
> possibility... not volunteering :) ]

/me wants a global $dbh that mimics the DBI interface but just uses SPI under the hood. Not volunteering, either…

David