Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Alex Hunsaker <badalex@gmail.com>

Cc: Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, Tim Bunce <Tim.Bunce@pobox.com>, pgsql-hackers@postgresql.org

Date: 2010-02-03T14:55:11Z

Lists: pgsql-hackers

On Wed, Feb 3, 2010 at 9:51 AM, Alex Hunsaker <badalex@gmail.com> wrote:
> Hey! I don't think were quite to that nasty B word yet :)  I would
> argue that treating plperl and plperlu as the same language just
> because it shares the same code is a mistake.  But I hate the idea of
> two custom_variable_classes for plperl(u) as well.  Which is why I
> quickly switched to plperl.on_plperl(u)_init.  Any thoughts on those?
> Again maybe people think the original names are fine... *shrug*.

I like plperl.on_plperl(u)_init better than plperl.on_(un)trusted_init.

...Robert