Tom Lane wrote:
Hmph ... looks like plperl is shy a few SPI_push/SPI_pop calls.
I've applied a patch for this --- it'll be in the next set of update
releases.
Great. Thanks a lot! The whole PostgreSQL stuff is really amazing! :-)
Regards,
Christian
--
Deriva GmbH
I wrote:
> =?ISO-8859-1?Q?Christian_Schr=F6der?= writes:
>> When I try to call the function I get the following error message:
>> test=# select * from testfunc();
>> ERROR: error from Perl function: SPI_connect failed: SPI_ERROR_CONNECT
>> at line 2.
> Hmph ... looks like plperl is shy a few S
=?ISO-8859-1?Q?Christian_Schr=F6der?= writes:
> When I try to call the function I get the following error message:
> test=# select * from testfunc();
> ERROR: error from Perl function: SPI_connect failed: SPI_ERROR_CONNECT
> at line 2.
Hmph ... looks like plperl is shy a few SPI_push/SPI_pop c
Hi list,
I have found the following problem: I have declared a domain datatype
with a check constraint. The check constraint uses a plpgsql function:
CREATE FUNCTION domain_ok(value integer) RETURNS boolean AS $$
BEGIN
RETURN value > 0;
END;
$$ LANGUAGE plpgsql;
CREATE DOMAIN testdomain int
