Re: why does plperl cache functions using just a bool for is_trigger - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: why does plperl cache functions using just a bool for is_trigger
Date
Msg-id B5A12283-CD39-4374-91D8-FDF299D8197A@kineticode.com
Whole thread Raw
In response to Re: why does plperl cache functions using just a bool for is_trigger  (Alex Hunsaker <badalex@gmail.com>)
Responses Re: why does plperl cache functions using just a bool for is_trigger
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: why does plperl cache functions using just a bool for is_trigger
Next
From: Alvaro Herrera
Date:
Subject: Re: ALTER OBJECT any_name SET SCHEMA name