Re: GRANT ON ALL IN schema

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Sam Mason <sam(at)samason(dot)me(dot)uk>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: GRANT ON ALL IN schema
Date: 2009-08-15 23:15:39
Message-ID: 1250378139.18992.6.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On lör, 2009-08-15 at 23:31 +0100, Sam Mason wrote:
> On Sat, Aug 15, 2009 at 11:34:04PM +0200, Dimitri Fontaine wrote:
> > Nitpicking dept, I think I prefer:
> >
> > DO [ [LANGUAGE] language] $$ ... $$;
> > DO plperl $$ ... $$;
> > DO language plpython $$ ... $$;
> >
> > language is optional and defaults to plpgsql.
>
> Yup, sounds nicer. The less globals the better!
>
> Next all you need is to be able to PREPARE them (and somehow access the
> parameters from execute) and you'll have nice local functions. :)

Yeah, rather than just making up some new command for "execute this
string", this could be generalized as lambda expressions that could be
called whereever an expression is allowed. E.g.

SELECT LAMBDA $$ ... $$;

-- if CALL is implemented
CALL LAMBDA $$ ... $$;

PREPARE foo AS SELECT LAMBDA $$ ... $$;
EXECUTE foo;

SELECT (LAMBDA (x int, y text) $$ ... $$) (37, 'foo');

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2009-08-15 23:24:54 Re: [COMMITTERS] pgsql: Remove tabs from SGML.
Previous Message Andrew Dunstan 2009-08-15 23:13:42 Re: [COMMITTERS] pgsql: Remove tabs from SGML.