On Wed, 13 Dec 2006, Martijn van Oosterhout wrote:
On Wed, Dec 13, 2006 at 05:04:42PM -0500, Tom Lane wrote:
Bricklen Anderson <[EMAIL PROTECTED]> writes:
Marc Evans wrote:
OK, I must be missing something obvious:
ERROR: creation of Perl function failed: 'eval "string"' trapped by
operation
On Wed, Dec 13, 2006 at 05:04:42PM -0500, Tom Lane wrote:
> Bricklen Anderson <[EMAIL PROTECTED]> writes:
> > Marc Evans wrote:
> >> OK, I must be missing something obvious:
> >> ERROR: creation of Perl function failed: 'eval "string"' trapped by
> >> operation mask at line 2.
>
> > Try as plper
Bricklen Anderson <[EMAIL PROTECTED]> writes:
> Marc Evans wrote:
>> OK, I must be missing something obvious:
>> ERROR: creation of Perl function failed: 'eval "string"' trapped by
>> operation mask at line 2.
> Try as plperlu
This brings up the question of whether it'd be safe to allow eval in
Marc Evans wrote:
OK, I must be missing something obvious:
c3i=> CREATE OR REPLACE FUNCTION foo_trigger() RETURNS TRIGGER AS $$
c3i$> eval { spi_exec_query('INSERT INTO FOO_BAR VALUES(1)'); } ||
c3i$> spi_exec_query('SELECT 1 as foo');
c3i$> $$ LANGUAGE plperl;
ERROR: creation of Perl funct
On Wed, 13 Dec 2006, Tom Lane wrote:
Marc Evans <[EMAIL PROTECTED]> writes:
Is it accurate for me to believe that there is no way to catch exception
within plperl?
You do it the same way you trap any other error in perl ...
OK, I must be missing something obvious:
c3i=> CREATE OR REPLACE
Marc Evans <[EMAIL PROTECTED]> writes:
> Is it accurate for me to believe that there is no way to catch exception
> within plperl?
You do it the same way you trap any other error in perl ...
regards, tom lane
---(end of broadcast)-
