Re: On defining Perl functions within PLPERL code - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: On defining Perl functions within PLPERL code
Date
Msg-id 59040ae3f7cfc1e3fc9bd8d871a3d5c3@biglumber.com
Whole thread Raw
In response to On defining Perl functions within PLPERL code  ("Kynn Jones" <kynnjo@gmail.com>)
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> I thought this claim needs further clarification, since the docs for PLPERL
> include a warning that may give readers the impression that defining Perl
> functions within PLPERL code is somehow problematic.  This warning says:

Well, it /is/ problematic, especially for those that don't know Perl well,
but doc patches are welcome. :)

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200803111136
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkfWpxIACgkQvJuQZxSWSsjG8ACgtm/KDquzv8kz0D3Ij4jHJvIG
HNgAoNS5sBTDfXjINj4TEsZdlEAi7mhM
=7pgP
-----END PGP SIGNATURE-----



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Database OID xxxxx now seems to belong to "foo"
Next
From: Alvaro Herrera
Date:
Subject: Re: Database OID xxxxx now seems to belong to "foo"