Re: auditing in postgresql

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Jeff Davis" <pgsql(at)j-davis(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: auditing in postgresql
Date: 2007-08-31 17:45:16
Message-ID: b42b73150708311045s33b4c41cn4cc5e05f940b0883@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 8/31/07, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Thu, 2007-08-30 at 21:43 -0400, Merlin Moncure wrote:
> > Well, a SRF may be unsuitable for various reasons, but maybe views are
> > better. I really like views more and more lately (better than
> > functions as a rule, I think).
> >
> > you have some query, select yadda
> > create view log_yadda as
> > select yadda
> > union all select null, null, null from log_func();
> >
>
> Interesting idea, I hadn't thought of that. Not perfect, but
> interesting.

create function func() returns bool as
$$
begin
raise notice 'log!';
return true;
end;
$$ language plpgsql;

how about this:
create view log_yadda sa
select yadda where (select func());

the parens around the function call force it to be evaluated as a scalar.

:-)

merlin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2007-08-31 17:51:23 Re: auditing in postgresql
Previous Message Jeff Davis 2007-08-31 17:08:26 Re: auditing in postgresql